Skip to content

release: 2.0.0 - #55

Open
bfrancojr wants to merge 1 commit into
mainfrom
release/v2.0.0
Open

bfrancojr wants to merge 1 commit into
mainfrom
release/v2.0.0

Conversation

@bfrancojr

Copy link
Copy Markdown
Collaborator

Prepares the 2.0.0 release. Once this merges, tagging v2.0.0 on main runs publish.yml, which publishes to PyPI.

  • pyproject.toml and protowire.__version__ go from 1.1.0 to 2.0.0.
  • CHANGELOG.md: [Unreleased] and the 1.1.0 section, which was never tagged, become one [2.0.0] — 2026-11-08 section. The section opens by saying why it is a major release. The two ### Added lists under Unreleased are merged. protowire-cpp did the same in v2.0.0 with its untagged 1.2.1.

Why 2.0.0. Three changes break existing callers:

The owner chose 2.0.0 on 2026-11-08.

Checked. I sorted the old and new changelog lines and diffed them. Every line is kept. The only changes are the new intro, one blank line, and the 1.1.0 entry "Built against protowire-cpp v1.2.0 in CI and the wheels", which now reads "(#23), on the way to v2.1.0". The release builds against v2.1.0, so the old wording was no longer true. git grep finds no other 1.1.0 version string.

Main's CI at b779fbd passed all 15 jobs, including the cibuildwheel smoke builds on Linux, macOS and Windows. This PR's own CI is pending.

Fold the never-tagged 1.1.0 section and [Unreleased] into [2.0.0], and
bump pyproject.toml and __version__. A major version because the Cell
type, bind_row's no-clear binding and skip_validate=False break existing
callers, as protowire-cpp v2.0.0 folded its untagged 1.2.1.
@bfrancojr

Copy link
Copy Markdown
Collaborator Author

CI on head ae70aba passed all 18 checks. That covers tests on Linux, macOS and Windows for Python 3.10–3.13, the cibuildwheel smoke builds on all three systems, and CodeQL for C++ and Python. Ready to merge. After the merge, the next steps are the annotated tag v2.0.0 on the merge commit, then gh release create with the 2.0.0 changelog section as notes.

This branch has not been deployed

No deployments
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