Increment version for 2.7.3 #66
Comments
github-actions bot
pushed a commit
that referenced
this issue
May 5, 2023
Signed-off-by: Peter Nied <petern@amazon.com>
github-actions bot
pushed a commit
that referenced
this issue
May 5, 2023
Signed-off-by: Peter Nied <petern@amazon.com>
github-actions bot
pushed a commit
that referenced
this issue
May 5, 2023
Signed-off-by: Peter Nied <petern@amazon.com>
peternied
added a commit
that referenced
this issue
May 5, 2023
This change alters the version workflow to create a new issue, then create several commits linked back to that issue and finally close the issue when all commits are completed for tracability of version updates. Background As version updates have different propigation speeds depending on pull request reviews, consistant CI in many branches, and an careful order of execution this would cause failures outside the scope of changes that would block changes into main and other branches. This change removes the use of pull requests and the standard ci gates. To ensure that the changes operate consistantly created a GitHub Action to manage the file modification peternied/opensearch-core-version-updater See an example of this workflows results with #66 Related issues - Resolves opensearch-project#7411 - Related Discussion opensearch-project#7398 - Resolves opensearch-project#7396 Signed-off-by: Peter Nied <petern@amazon.com>
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue for tracking the changes associated with a version increment.
The text was updated successfully, but these errors were encountered: