Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Make sure each merge is a version bump #13

Closed
peterzhuamazon opened this issue Sep 30, 2024 · 1 comment · Fixed by #14, #16 or #18
Closed

[Enhancement] Make sure each merge is a version bump #13

peterzhuamazon opened this issue Sep 30, 2024 · 1 comment · Fixed by #14, #16 or #18
Assignees
Labels

Comments

@peterzhuamazon
Copy link
Member

We want to make sure each merge include a version bump, so that the docker image and potential future releases can be correctly versioned.

We also want to make sure a new version bump will not affect an older version during runtime.

Thanks.

@peterzhuamazon peterzhuamazon added enhancement New feature or request version labels Sep 30, 2024
@peterzhuamazon peterzhuamazon self-assigned this Sep 30, 2024
@peterzhuamazon peterzhuamazon moved this from 🆕 New to 👀 In review in Engineering Effectiveness Board Sep 30, 2024
@peterzhuamazon peterzhuamazon moved this from Backlog to In review in OpenSearch Engineering Effectiveness Sep 30, 2024
@peterzhuamazon peterzhuamazon moved this from 👀 In review to 🏗 In progress in Engineering Effectiveness Board Sep 30, 2024
@peterzhuamazon peterzhuamazon moved this from In review to In Progress in OpenSearch Engineering Effectiveness Sep 30, 2024
@github-project-automation github-project-automation bot moved this from 🏗 In progress to ✅ Done in Engineering Effectiveness Board Oct 1, 2024
@peterzhuamazon peterzhuamazon reopened this Oct 2, 2024
@github-project-automation github-project-automation bot moved this from ✅ Done to 🏗 In progress in Engineering Effectiveness Board Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment