-
Notifications
You must be signed in to change notification settings - Fork 277
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] Re-release workflow should use corresponding tag in opensearch-build to do re-release instead of main branch #4367
Labels
Comments
github-project-automation
bot
moved this to Backlog
in OpenSearch Engineering Effectiveness
Jan 23, 2024
peterzhuamazon
moved this from Backlog
to In Progress
in OpenSearch Engineering Effectiveness
Jan 23, 2024
github-project-automation
bot
moved this from In Progress
to Done
in OpenSearch Engineering Effectiveness
Feb 1, 2024
2PR with @zelinh on 20240201 to re-release 1.3.14 and 2.11.1 version. Confirmed that build is using the corresponding tag instead of main:
Without security admin:admin changes in here: opensearch-project/security#3622
|
github-project-automation
bot
moved this from Done
to Not started
in OpenSearch Engineering Effectiveness
Feb 1, 2024
github-project-automation
bot
moved this from Not started
to Done
in OpenSearch Engineering Effectiveness
Feb 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[Enhancement] Re-release workflow should use corresponding tag in opensearch-build to do re-release instead of main branch.
The current changes in security plugin caused a lot of changes in
main
branch of opensearch-build: opensearch-project/security#3624. If we bound to re-release older versions of docker images, we would like to use the corresponding tag code to release, instead of introducing new changes from main back to older version, such as config and entrypoint changes.Thanks.
The text was updated successfully, but these errors were encountered: