Skip to content

ci: retire bcbpy compatibility publishing - #26

Merged
rteoo merged 1 commit into
mainfrom
chore/retire-bcbpy-publishing
Nov 10, 2026
Merged

rteoo merged 1 commit into
mainfrom
chore/retire-bcbpy-publishing

Conversation

@rteoo

@rteoo rteoo commented Nov 10, 2026

Copy link
Copy Markdown
Owner

Summary

  • Publish only bcb-data from PyPI and TestPyPI workflows, and build/smoke-test only the canonical distribution in CI and the local release helper.
  • Freeze the final bcbpy distribution at 2.5.0 with bcb-data==2.5.0; retain its source unchanged and remove the test requirement to track future canonical versions.
  • Document the final compatibility release and archival policy in the README, migration guide, and project instructions.

Testing

  • 157 offline tests and 9 subtests passed; live integration tests excluded.
  • Simulated bcb-data 2.6.0 in a disposable source copy while leaving compat/bcbpy unchanged: sdist/wheel builds, strict Twine checks, the CI wheel glob/import command, and all 157 offline tests passed.
  • Parsed all workflows and verified that only canonical publishing remains, with existing OIDC permissions, artifact paths, and environments preserved.
  • Confirmed no compatibility source or metadata files changed. Hosted CI is pending.

Risks

  • bcbpy 2.5.0 remains pinned to bcb-data 2.5.0 and receives no further updates; users must install/import bcb-data/bcb_data directly for future releases.
  • The completed v2.5.0 release and its historical workflow are unchanged. No new package release, archive action, or access-control change is included.

@rteoo
rteoo merged commit ee5aff3 into main Nov 10, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant