Skip to content

release: v3.6.0.0 #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
birkholz-cubert merged 1 commit into from
Sep 11, 2026
Merged

release: v3.6.0.0 #42

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,10 @@ Pre-releases (`b*`, `rc*`) are not listed.

## [Unreleased]

## [3.6.0.0] - 2026-09-11

Compiled against cuvis SDK 3.6.0.

### Added

- `CI` - `.github/workflows/release.yml` is driven by `v*.*.*.*` tags: it validates the tag against `pyproject.toml`, this file and the `cuvis_base` images, builds the wheels, publishes to TestPyPI and PyPI, pushes the `cubertgmbh/cuvis_pyil` images, and creates a GitHub Release with the matching section here as notes.
Expand All @@ -34,6 +38,7 @@ Pre-releases (`b*`, `rc*`) are not listed.

### Changed

- `CONTRIBUTING.md` - the branch model is now trunk based: `develop` is gone, every change is cut from `main` and merged back into it by pull request, and a commit on `main` is no longer necessarily a release.
- One Linux wheel per Python version and architecture, built on the oldest Ubuntu that has a `cuvis_base` image, instead of one per Ubuntu release.
A `manylinux` tag states a minimum glibc, so the 22.04 build already served 24.04 and 26.04; the second wheel only ever duplicated it.
- The platform tag now comes from `auditwheel`, which derives it from the symbols the extension references and fails the build when they outgrow the tag, instead of being stamped from the build container.
Expand Down
10 changes: 5 additions & 5 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,12 +7,12 @@ For bug reports and questions use [GitHub Issues](https://github.com/cubert-hype

| Branch | Role |
| --- | --- |
| `main` | The latest released interface layer for the latest released cuvis SDK. Every commit on `main` is a release and carries a `v*` tag. Never receives direct pushes. |
| `develop` | Integration branch for the next release. All feature work lands here. |
| `feature/*` | One branch per change, cut from `develop`, merged back into `develop` by pull request. |
| `hotfix/*` | Cut from `main` when a released version needs a fix before `develop` is ready to release. Merged into `main` by pull request, tagged, then merged back into `develop`. |
| `main` | Trunk, and the latest released interface layer for the latest released cuvis SDK. Never receives direct pushes. |
| `feature/*` | One branch per change, cut from `main`, merged back into `main` by pull request. |

A pull request into `develop` or `main` must pass the `ci.yml` build and changelog jobs.
A release is a `v*` tag on a commit of `main`; not every commit on `main` is a release.

A pull request into `main` must pass the `ci.yml` build and changelog jobs.

## Version scheme

Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"

[project]
name = "cuvis_il"
version = "3.6.0.0rc1"
version = "3.6.0.0"
description = "Compiled Python Bindings for the CUVIS SDK."
readme = "README.md"
requires-python = ">=3.10"
Expand Down
Loading