fix(ci): release-plz determines releases from git tags (git_only) + cut v0.1.6#61
Merged
Merged
Conversation
…rsion reqs Without git_only, release-plz consults the cargo registry; pds is never published, so every version looked perpetually unreleased and release-pr proposed the current version forever instead of bumping (hence the manual bump PRs #29/#31/#33/#47/#60). git_only resolves the last release from the v* tags. The internal path deps gain version requirements because git_only mode runs cargo package, which rejects versionless path deps; resolution is unchanged (path wins inside the workspace) and release-plz bumps the requirements on release. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The git_only content diff packages the latest tag's tree; v0.1.5 predates the dep version requirements, so the automation only heals once this tag exists. From v0.1.6 on, release-plz proposes version bumps itself. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Deploying pseudoscript-landing with
|
| Latest commit: |
cc6efd7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7130cfc7.pseudoscript-landing.pages.dev |
| Branch Preview URL: | https://fix-release-plz-git-only.pseudoscript-landing.pages.dev |
Deploying pseudoscript-ide with
|
| Latest commit: |
cc6efd7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8b7be99a.pseudoscript-ide.pages.dev |
| Branch Preview URL: | https://fix-release-plz-git-only.pseudoscript-ide.pages.dev |
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
1 participant
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.
release-plz never bumped versions because, with nothing on crates.io, it consulted the registry, found nothing, and proposed the current version forever — every release needed a manual bump PR (#29, #31, #33, #47, #60). This makes the automation self-sufficient:
release-plz.toml:git_only = trueon thepseudoscriptpackage — the last release is resolved from thev*tags instead of the registry.git_only's next-version step runscargo package, which rejects versionless path deps. All 34 internal path deps gainversion = "0.1.6"; resolution is unchanged (path wins inside the workspace) and release-plz bumps the requirements on release.build.rs/main.rs: thecargo packageverify build compiles from a tarball without the repo-levelLANG.md/CONFORMANCE//SKILL.md. The skill is now staged intoOUT_DIRbybuild.rslike the lang bundle, and both fall back to a stub outside the repo (the crate is never published, so only throwaway verify builds hit the stub).chore: release v0.1.6: the content diff packages the latest tag's tree, and v0.1.5 predates the dep version requirements — the automation only heals once a tag containing this fix exists. Merging this PR cuts v0.1.6 via the existing pipeline; from then on release-plz proposes bumps itself.Validated locally with release-plz 0.3.159 (the version the action installs):
release-plz updateagainst a tag containing the fix: packages cleanly, proposes no release for zero commits since the tag, and proposes a real bump (Cargo.toml 0.1.5 → 0.1.6 + changelogs + lock) for afix:commit after it.release-plz release --dry-runin exactly this merge state: would create tagv0.1.6+ the GitHub release; library crates correctly report "no release method enabled".pds langandpds skillverified to still print the real bundle/skill from repo builds; fmt/clippy/tests/model-conformance green.🤖 Generated with Claude Code