selu/ir-bt-bridge
Watch
1
0
Fork
You've already forked ir-bt-bridge
 0
Code Issues Pull requests Projects Releases 3 Packages 4 Wiki Activity Actions

Link the published crates to the repo in the release #6

Merged
selu merged 1 commit from link-packages into master 2026-10-30 08:13:59 +00:00
Conversation 0 Commits 1 Files changed 1 +23 -1
selu commented 2026-10-30 07:59:21 +00:00
Owner

Summary

Forgejo packages belong to the user, and cargo publish doesn't link them to a repo, so the v0.2.2 crates were missing from this repo's Packages tab. The release's crates job now links each crate to the repo after publishing.

  • The step skips crates that are already linked, checked with a GET of the package, and fails if a crate is still unlinked after the link call.
  • It uses CARGO_REGISTRY_TOKEN as a plain token, without cargo's Bearer prefix.
  • The crate list is duplicated from the Publish step, with a comment in that step to keep the two in sync.

Testing

  • The workflow YAML parses, and the link check matches the four crates, which are already linked to selu/ir-bt-bridge.
  • The link call itself runs for the first time on the next release tag.

🤖 Generated with Claude Code

## Summary Forgejo packages belong to the user, and `cargo publish` doesn't link them to a repo, so the v0.2.2 crates were missing from this repo's Packages tab. The release's `crates` job now links each crate to the repo after publishing. - The step skips crates that are already linked, checked with a `GET` of the package, and fails if a crate is still unlinked after the link call. - It uses `CARGO_REGISTRY_TOKEN` as a plain `token`, without cargo's `Bearer` prefix. - The crate list is duplicated from the Publish step, with a comment in that step to keep the two in sync. ## Testing - The workflow YAML parses, and the link check matches the four crates, which are already linked to `selu/ir-bt-bridge`. - The link call itself runs for the first time on the next release tag. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Link the published crates to the repo in the release
All checks were successful
Continuous Integration / Firmware (pull_request) Successful in 4m20s
Details
Continuous Integration / Firmware-1 (pull_request) Successful in 14m37s
Details
Continuous Integration / Host tools (pull_request) Successful in 45s
Details
Continuous Integration / Host tools-1 (pull_request) Successful in 54s
Details
Continuous Integration / Firmware-2 (pull_request) Successful in 12m4s
Details
Docs / Docs (pull_request) Successful in 2m35s
Details
Continuous Integration / Host tools-2 (pull_request) Successful in 49s
Details
7efcc1cc6d 
Forgejo packages belong to the user, and `cargo publish` doesn't link
them to a repo, so they were missing from the repo's Packages tab. Link
each crate after publishing, skipping ones that are already linked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
selu merged commit 21a1ba2dd9 into master 2026-10-30 08:13:59 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
selu/ir-bt-bridge!6
No description provided.