fix(release): add missing description to incredible-squaring-blueprint-lib#1436
Merged
Merged
Conversation
…t-lib PR #1435's Release Plz run partially failed: ✓ blueprint-manager 0.4.0-alpha.8 — published ✓ cargo-tangle 0.5.0-alpha.8 — published ✗ incredible-squaring-blueprint-lib 0.2.0-alpha.8 — 400 from crates.io: "missing or empty metadata fields: description" Sibling example crates (incredible-squaring-eigenlayer, hello-tangle, apikey-blueprint-lib, oauth-blueprint-lib) all carry an explicit package-level description; this one was the only published example missing it. The workspace's [workspace.package] correctly omits `description` so each package owns its own copy. After this merges, re-trigger Release Plz to land the 0.2.0-alpha.8 publish; the version is reservable since crates.io rejected at the metadata-validation stage, not after acceptance.
PR Quality Gate Summary
Blocking issues
|
2 tasks
drewstone
added a commit
that referenced
this pull request
May 23, 2026
….9 (#1437) * fix(release): add missing description to incredible-squaring-blueprint-lib PR #1435's Release Plz run partially failed: ✓ blueprint-manager 0.4.0-alpha.8 — published ✓ cargo-tangle 0.5.0-alpha.8 — published ✗ incredible-squaring-blueprint-lib 0.2.0-alpha.8 — 400 from crates.io: "missing or empty metadata fields: description" Sibling example crates (incredible-squaring-eigenlayer, hello-tangle, apikey-blueprint-lib, oauth-blueprint-lib) all carry an explicit package-level description; this one was the only published example missing it. The workspace's [workspace.package] correctly omits `description` so each package owns its own copy. After this merges, re-trigger Release Plz to land the 0.2.0-alpha.8 publish; the version is reservable since crates.io rejected at the metadata-validation stage, not after acceptance. * chore(release): bump incredible-squaring-blueprint-lib 0.2.0-alpha.8 → alpha.9 release-plz tagged v0.2.0-alpha.{5,6,7,8} but cargo publish failed silently each time on a missing description metadata field. crates.io still has 0.2.0-alpha.4 as the latest live version. PR #1436 fixed the description. But release-plz now sees the v0.2.0-alpha.8 tag and considers it already released, so it won't retry that version. Bumping to alpha.9 gives release-plz a tag-less target — it creates v0.2.0-alpha.9 and cargo publish lands the crate. Also bumps the workspace-dependency pin so internal references stay honest. --------- Co-authored-by: Drew Stone <drewstone329@gmail.com>
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
2 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
Fixes the Release Plz failure on PR #1435's merge.
The release-plz run in #1435 was 2-for-3:
incredible-squaring-blueprint-libwas the only published example crate without a package-leveldescription. Workspace inheritance ([workspace.package]) intentionally omitsdescriptionso each crate owns its own, matching the convention used byincredible-squaring-eigenlayer,hello-tangle,apikey-blueprint-lib, andoauth-blueprint-lib.After merge
The
0.2.0-alpha.8version is still reservable — crates.io rejected at the metadata-validation stage before accepting the upload, so the version number isn't burned. Re-trigger Release Plz with:…and the publish should land on the first try.
Test plan
descriptionresolves at the package level,licensestill inherits from workspace)incredible-squaring-blueprint-lib v0.2.0-alpha.8lands on crates.io