Repository navigation
release: v3.6.0 - #8
Merged
Merged
Conversation
Close the changelog section for 3.6.0 and record that cuvis_base packages cuvis SDK 3.6.0.
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
## [Unreleased]becomes## [3.6.0] - 2026-09-11, with a fresh empty## [Unreleased]above it.`cuvis_base` - packages cuvis SDK 3.6.0.under### Changed, matching how[3.5.3]records the SDK it packages.Why
validatejob refuses to release unless the newest changelog section is the version being tagged and## [Unreleased]is empty.Notes
release.ymlfeedsgithub.ref_nametorelease-meta, unlike cuvis.pyil and cuvis.python which read[project].versionfrompyproject.toml.developbranch from the branch model. Nothing to do for that here: the only occurrence of the word in this repository is "application development" in the README boilerplate, and there is noCONTRIBUTING.md. If the branch model should be written down for this repository too, that is a separate change.check_changelog.py --version 3.6.0passes.Pitfalls
v3.6.0tag is pushed onmain, and that has to happen before the cuvis.pyil and cuvis.python releases, which both gate on thecuvis_baseimages this produces.https://cloud.cubert-gmbh.de/s/cuvis_sdk_release_ver_360/downloadbefore tagging. TheDownload the SDK releasestep fails otherwise, and the equivalent step in cuvis.pyil is failing on this right now.Companion pull requests