Repository navigation
release: v3.6.0.0 - #99
Merged
Merged
Conversation
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.
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.
What
[project].versionfrom3.6.0.0rc2to the final3.6.0.0.cuvis-ilrequirement from>=3.6.0a0,<3.7.0to>=3.6.0,<3.7.0.## [Unreleased]becomes## [3.6.0.0] - 2026-09-11with the SDK statement lines, and a fresh empty## [Unreleased]sits above it.developfrom the branch model inCONTRIBUTING.mdandREADME.md. The repository moves to a trunk based flow:feature/*is cut frommainand merged back intomainby pull request.Why
a0bound exists so a pre-release wrapper can resolve a pre-release interface layer. PEP 440 sorts3.6.0.0rc1below3.6.0, so a plain>=3.6.0bound cannot reach one and no--preflag changes that. The flag it sets applies to the whole range, so leavinga0in place on a final release makes pip prefer a pre-release of a later SDK,3.6.1.0rc1, over the current final3.6.0.0. Hence the flip.developis no longer used, so documenting it sends contributors to a branch nobody maintains.Notes
Verify the cuvis-il requirement agrees with the versionstep inrelease.ymlenforces 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.check_changelog.py --version 3.6.0.0passes,ruff format --check .andruff check .pass.a0bound, so the published notes describe what actually shipped.hotfix/*is gone from the table and theHotfix release from mainsection is nowFixing a released version.hotfix/*only existed to describe fixingmainwhiledevelopwas not ready to release; withoutdevelopit is an ordinaryfeature/*branch. The step that mergedmainback intodevelopis gone with it.release/vX.Ystays; it is a maintenance branch for older SDK lines and is unrelated todevelop.Pitfalls
ci.ymlstill triggers on pushes and pull requests todevelop. 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.mdstill states that thepypienvironment 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.vX.Y.Z.Wtag is pushed onmain, andcuvis.pyil3.6.0.0 has to be on PyPI first or the dependency will not resolve.