Skip to content

release: v3.6.0.0 - #99

Merged
birkholz-cubert merged 1 commit into
mainfrom
feature/release-3.6.0.0
Sep 11, 2026
Merged

birkholz-cubert merged 1 commit into
mainfrom
feature/release-3.6.0.0

Conversation

@birkholz-cubert

@birkholz-cubert birkholz-cubert commented Sep 11, 2026 •

Copy link
Copy Markdown
Collaborator

What

  • Bump [project].version from 3.6.0.0rc2 to the final 3.6.0.0.
  • Close the cuvis-il requirement from >=3.6.0a0,<3.7.0 to >=3.6.0,<3.7.0.
  • Close the changelog: ## [Unreleased] becomes ## [3.6.0.0] - 2026-09-11 with the SDK statement lines, and a fresh empty ## [Unreleased] sits above it.
  • Drop develop from the branch model in CONTRIBUTING.md and README.md. The repository moves to a trunk based flow: feature/* is cut from main and merged back into main by pull request.

Why

  • 3.6.0.0 is the final release for cuvis SDK 3.6.0; the rc line is done.
  • The a0 bound exists so a pre-release wrapper can resolve a pre-release interface layer. PEP 440 sorts 3.6.0.0rc1 below 3.6.0, so a plain >=3.6.0 bound cannot reach one and no --pre flag changes that. The flag it sets applies to the whole range, so leaving a0 in place on a final release makes pip prefer a pre-release of a later SDK, 3.6.1.0rc1, over the current final 3.6.0.0. Hence the flip.
  • develop is no longer used, so documenting it sends contributors to a branch nobody maintains.

Notes

  • The Verify the cuvis-il requirement agrees with the version step in release.yml enforces this flip and would have failed the release had the bound been left open. Checked locally against this diff: accepts SDK 3.6.0, pre-release agreement holds.
  • Validated locally: check_changelog.py --version 3.6.0.0 passes, ruff format --check . and ruff check . pass.
  • The release section for the flip is worded as the final bound, replacing the earlier entry that described the a0 bound, so the published notes describe what actually shipped.
  • hotfix/* is gone from the table and the Hotfix release from main section is now Fixing a released version. hotfix/* only existed to describe fixing main while develop was not ready to release; without develop it is an ordinary feature/* branch. The step that merged main back into develop is gone with it.
  • release/vX.Y stays; it is a maintenance branch for older SDK lines and is unrelated to develop.

Pitfalls

  • ci.yml still triggers on pushes and pull requests to develop. That is outside the scope asked for here, and it is dead config rather than a bug, but it should be cleaned up in a follow-up so the workflow and the contribution guide agree.
  • CONTRIBUTING.md still states that the pypi environment carries required reviewers that gate the PyPI publish. Worth confirming that is actually configured before tagging, since the environment was recently reconfigured for tag based deployments.
  • Merging this does not release anything. The release starts when a vX.Y.Z.W tag is pushed on main, and cuvis.pyil 3.6.0.0 has to be on PyPI first or the dependency will not resolve.

Bump the version from 3.6.0.0rc2 to the final 3.6.0.0 and close the
changelog section for it.

Close the cuvis-il requirement from >=3.6.0a0 to >=3.6.0. The a0 bound
exists so a pre-release wrapper can resolve a pre-release interface layer;
left in place on a final release it makes pip prefer a pre-release of a
later SDK over the current final.

Drop the develop branch from the branch model; the repository moves to a
trunk based flow where feature branches are cut from main and merged back
into it.

@manke-cubert manke-cubert left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 🚀

@birkholz-cubert
birkholz-cubert merged commit 0a994f5 into main Sep 11, 2026
7 of 8 checks passed
@birkholz-cubert
birkholz-cubert deleted the feature/release-3.6.0.0 branch September 11, 2026 19:47
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.

2 participants