ci: automate extension upgrade scripts creation #310
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
This PR is to automate the extension upgrade scripts creation.
What is the current behavior?
When a new version is released, we need to manually change the
release.ymlworkflow to add a command for previous version upgrade script. Although this manual process is written in playbook, it is tedious and sometimes missed during release. If a certain version upgrade script is missing, it will cause upgrade issue for database with that legacy version of wrappers.What is the new behavior?
Add a shell script to automate the upgrade script creation process, so it won't missing any previous version upgrade script.
Additional context
N/A