You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(release): bump workspace-dependency pins to 0.1.15-rc.5 (#1039)
* chore(release): bump workspace-dependency version pins to 0.1.15-rc.5
The rc.5 cut bumped workspace.package.version but left the 11
[workspace.dependencies] kornia-* pins at rc.4 — locally the path
component wins so builds pass, but published crates would declare
^0.1.15-rc.4 inter-crate requirements instead of rc.5, diverging from
release practice (rc.4's cut bumped both).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(release): guard workspace-dependency pins against version drift
scripts/check_version_pins.py fails when any kornia-* pin in
[workspace.dependencies] disagrees with workspace.package.version;
wired as a pre-commit hook on Cargo.toml. Release skill step 4 now
spells out the both-places rule and the diff-shape sanity check.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(cargo): explain the version-pin bump rule at the point of edit
Replaces the stale kornia-py note (kornia-py inherits
workspace.package.version since the workspace=true migration — verified
via cargo metadata) with the actual trap: the kornia-* dependency pins
below cannot inherit the workspace version and must be bumped with it,
enforced by scripts/check_version_pins.py.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* chore(release): regenerate kornia-cpp version.hpp; guard covers it
kornia-cpp commits its build.rs-generated version header for pure-CMake
consumers — it was still rc.4. Regenerated to rc.5;
check_version_pins.py now also validates it, and the release skill
documents the cpp step (kornia-py needs nothing: workspace-inherited +
pyproject dynamic version).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* docs(release): version.hpp is gitignored — correct the guard/skill wording
The header is regenerated by build.rs and never committed; the stale
copy was a local artifact, not a shipped bug. Keep the guard's check as
a pre-release freshness sanity for by-hand CMake builds.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
0 commit comments