chore(release): v0.2.0 - #80
Conversation
The `test-util` self dev-dependency inherited the workspace entry, which
carries a version requirement. At package time cargo resolves that against
the registry rather than the local path, so `cargo package` failed before
anything could be uploaded:
failed to select a version for the requirement
`praxis-policy-apl-core = "^0.2.0"`
candidate versions found which didn't match: 0.1.0
Point it at the crate's own directory with no version instead. Cargo drops a
dev-dependency naming no version from the published manifest, which is correct
here because no consumer builds this crate's tests. The feature, the test seam
and the 435 tests that use it are unchanged.
This would have failed the release workflow's verify job after the tag was
already pushed.
Signed-off-by: Frederico Araujo <frederico.araujo@ibm.com>
Minor rather than patch. This release removes public API and ten config keys, and cargo-semver-checks reports 24 breaking changes across five crates (praxis-policy-core, -apl-core, -apl-runtime, -plugin-identity-jwt, -plugin-delegator-oauth). Under cargo's 0.x rules 0.1.1 would be a compatible upgrade, so every consumer on `0.1` would take those changes without opting in. The README already states that a breaking change gets a minor bump. Cut the CHANGELOG's [Unreleased] section to [0.2.0], add its compare link, and move the README's dependency snippet, requirement note and status to 0.2. Signed-off-by: Frederico Araujo <frederico.araujo@ibm.com>
praxis-bot
left a comment
praxis-bot
left a comment
There was a problem hiding this comment.
Release PR Review: v0.2.0
Purpose: Bumps all 16 crates from 0.1.0 to 0.2.0, cuts the CHANGELOG [Unreleased] section, updates README version references, and fixes a cargo package blocker in ppe-apl-core.
Assessment: Clean release PR. Version bumps are consistent across Cargo.toml workspace deps, Cargo.lock, README, and CHANGELOG. The dev-dependency fix in crates/ppe-apl-core/Cargo.toml is correct: a self dev-dependency with a version requirement fails cargo package because cargo resolves it against the registry where the new version does not yet exist. Switching to path-only is the right fix — cargo strips versionless dev-deps from the published manifest, so consumers are unaffected.
| Severity | Count |
|---|---|
| Critical | 0 |
| Large | 0 |
| Medium | 0 |
No issues found. The semver-checks output (24 breaking changes across five crates) justifies the minor bump under 0.x rules, and the CHANGELOG already documents the breaking changes from the [Unreleased] section.
Signed-off-by: Frederico Araujo <frederico.araujo@ibm.com>
2ff6e82 to
1fe0152
Compare
github-project-automation
Bot
moved this from Review
to Done
in Praxis Policy Engine (PPE)
3 participants
Prepares the 0.2.0 release.
Minor, not patch.
cargo-semver-checksreports 24 breaking changes across five crates (-core,-apl-core,-apl-runtime,-plugin-identity-jwt,-plugin-delegator-oauth), and the release removes ten config keys. Under cargo's 0.x rules0.1.1would reach every consumer on0.1without their opting in.Also fixes a release blocker.
cargo packagefailed onpraxis-policy-apl-core: itstest-utilself dev-dependency carried a version requirement, which cargo resolves against the registry rather than the local path. Introduced this cycle, it would have failed the release workflow's verify job after the tag was pushed. Now a path-only dev-dependency, which cargo strips from the published manifest.Version bump via
make release-version; CHANGELOG[Unreleased]cut to[0.2.0]; README moved to0.2.make publish-drymake lint--all-featuresmake auditMerge, then
make tag VERSION=0.2.0to trigger the publish.