Canary: strip -DEV suffix to release 0.2.0#3
Merged
Conversation
End-to-end test of the prerelease-batching feature merged in ITensor/ITensorActions#110: the strip-suffix release path (0.2.0-DEV → 0.2.0) should pass VersionCheck, fire Registrator, and have `is_breaking` derived against the last released version (0.1.0) via `find_last_released_version`.
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. Thanks for integrating Codecov - We've got you covered ☂️ |
This file contains hidden or 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.
Summary
End-to-end canary for the prerelease-batching feature merged in ITensor/ITensorActions#110: exercise the strip-suffix release path.
Expected behavior on this PR:
0.2.0-DEV → 0.2.0is the documented release transition.ITensorRegistryforITensorTestPackage v0.2.0.is_breaking: derived against the last released version (0.1.0) viafind_last_released_version, since0.2.0-DEVshares the bareM.m.pwith this release. With0.1.0as the reference, this is a pre-1.0 minor bump → breaking → release notes propagate to the registry PR and the GitHub release.v0.2.0tag and release.Release notes: