We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The command git-upgrade-shared-modules always updates the commands to the latest available version, which is not always the desired behaviour.
git-upgrade-shared-modules
For example, when releasing a new maintenance version for REANA 0.9, the script should not consider versions in the 0.95 release.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The command
git-upgrade-shared-modules
always updates the commands to the latest available version, which is not always the desired behaviour.For example, when releasing a new maintenance version for REANA 0.9, the script should not consider versions in the 0.95 release.
The text was updated successfully, but these errors were encountered: