Release v0.6.0 - #221
Merged
Merged
Conversation
|
|
The package build (reusable-build.yaml) ran on Python 3.9, but requires-python is >=3.10 since #214 dropped 3.9 support. `pip install -e .[build]` would abort on 3.9, breaking both the draft-release build and the PyPI publish build. The wheel is py3-none-any (pure Python), so any supported version builds an equivalent artifact. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
setuptools-scm was configured but never drove the version: `version` is declared statically in [project] and not listed in [project.dynamic], so setuptools uses the static field and ignores the scm plugin (confirmed: built metadata reports the static value, not a tag-derived dev version). The dead config only created ambiguity about where the version comes from. Removed [tool.setuptools_scm] and dropped setuptools-scm from build-system.requires and the build optional-dependencies. The package version is now unambiguously the static `version` field, bumped manually in release PRs. quam/_version.py is unaffected (it reads installed package metadata, not an scm-generated file). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Closed
This reverts commit 5588436.
yonatanrqm
approved these changes
Jun 18, 2026
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
3 participants
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.
Summary
Prepares the v0.6.0 release.
versionto0.6.0inpyproject.toml[Unreleased]changelog section to[v0.6.0](empty[Unreleased]retained on top, matching the prior release convention)reusable-build.yamlPython from3.9→3.12Missing changelog entries added
Audited all PRs merged since the v0.5.0 changelog (
ffa137e). The existing[Unreleased]section already covered #218 (__package_versions__), #211 (lo_mode), #210 (pulse deprecations +qualang-toolsremoval), and #209 (qualibrate save fix). The following were missing and have been added:PRs that are CI/test/docs-only and do not warrant changelog entries (consistent with existing changelog style): #215, #216, #212, #207.
Release build fix
reusable-build.yaml(used by both the draft-release and PyPI-publish workflows) pinnedsetup-pythonto3.9, butrequires-pythonhas been>=3.10since #214 dropped 3.9.pip install -e .[build]would abort on 3.9, breaking the release pipeline. Bumped to3.12; the wheel ispy3-none-anyso the artifact is equivalent on any supported version.🤖 Generated with Claude Code
Supersedes #220.