-
Notifications
You must be signed in to change notification settings - Fork 29
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
feat: upgrade changes #358
Conversation
dfd4025
to
e776cd3
Compare
e776cd3
to
36fbda1
Compare
36fbda1
to
3c561bb
Compare
Signed-off-by: Niladri Halder <[email protected]>
…le one Signed-off-by: Niladri Halder <[email protected]>
Signed-off-by: Niladri Halder <[email protected]>
Signed-off-by: Niladri Halder <[email protected]>
3c561bb
to
e954b4e
Compare
bors merge |
358: feat: upgrade changes r=niladrih a=niladrih <! Co-authored-by: Niladri Halder <[email protected]>
This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried. Additional information: Response status code: 422
{"message":"All comments must be resolved.","documentation_url":"https://docs.github.com/articles/about-protected-branches"} |
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Changes to upgrade.
Description
Changes:
--allow-unstable
flag. The existing flag--skip-upgrade-path-validation-for-unsupported-version
also skips this check.v2.5.0-0-main-unstable-<timestamp>-0
alongside the usual tag2.5.0-0-main-unstable-<timestamp>-0
.