Skip to content

release: v3.6.0.0 - #42

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.0rc1 to the final 3.6.0.0.
  • Close the changelog: ## [Unreleased] becomes ## [3.6.0.0] - 2026-09-11 with the Compiled against cuvis SDK 3.6.0. statement, and a fresh empty ## [Unreleased] sits above it.
  • Drop develop from the branch model in CONTRIBUTING.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.
  • develop is no longer used, so documenting it sends contributors to a branch nobody maintains.

Notes

  • The old branch model claimed every commit on main is a release and carries a v* tag. That is no longer true under a trunk based flow, so that sentence was replaced rather than deleted: a release is a v* tag on a commit of main, and not every commit is one.
  • Validated locally with the shared changelog action: check_changelog.py --version 3.6.0.0 passes, so the validate job's changelog gate is satisfied.
  • hotfix/* is gone from the table. It only existed to describe fixing main while develop was not ready to release; without develop it is an ordinary feature/* branch.

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. The CHANGELOG.md entry describing ci.yml still mentions develop because it accurately describes the workflow as it stands today.
  • Merging this does not release anything. The release starts when a vX.Y.Z.W tag is pushed on main.
  • The environments testpypi, pypi and dockerhub now all carry a v* policy of type tag, so the tag push will not be rejected.

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

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 2d8010e into main Sep 11, 2026
61 of 62 checks passed
@birkholz-cubert
birkholz-cubert deleted the feature/release-3.6.0.0 branch September 11, 2026 16:33
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