Repository navigation
ci: retire bcbpy compatibility publishing - #26
Merged
Merged
Conversation
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
bcb-datafrom PyPI and TestPyPI workflows, and build/smoke-test only the canonical distribution in CI and the local release helper.bcbpydistribution at 2.5.0 withbcb-data==2.5.0; retain its source unchanged and remove the test requirement to track future canonical versions.Testing
bcb-data2.6.0 in a disposable source copy while leavingcompat/bcbpyunchanged: sdist/wheel builds, strict Twine checks, the CI wheel glob/import command, and all 157 offline tests passed.Risks
bcbpy2.5.0 remains pinned tobcb-data2.5.0 and receives no further updates; users must install/importbcb-data/bcb_datadirectly for future releases.