Skip to content

Scratch: can fil-forge-bot read ghcr.io package versions? - #137

Closed
Peeja wants to merge 2 commits into
mainfrom
claude/happy-bell-cfh5qb-packages-probe
Closed

Peeja wants to merge 2 commits into
mainfrom
claude/happy-bell-cfh5qb-packages-probe

Conversation

@Peeja

@Peeja Peeja commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Written by Claude.

Scratch, not for merging. It will be closed once it has run.

Checks whether promote-staging.sh could link each digest to its ghcr.io package page, as discussed for #136. The page's URL needs the package version's numeric ID. Getting the ID from a digest takes the packages API (GET /orgs/fil-forge/packages/container/{package}/versions), and it's unclear whether the fil-forge-bot app token can call it.

.github/workflows/probe-packages.yml looks up dev's pinned piri and ingot digests with three tokens, and writes a table to the job summary:

  • the fil-forge-bot token, minted as promote-staging.yml mints it
  • the same app's token, asking for permission-packages: read. The mint itself fails if the app lacks that permission.
  • the workflow's own GITHUB_TOKEN with packages: read

The job fails if any lookup fails, so a red check here is a result, not a breakage.

✴️

🤖 Generated with Claude Code

https://claude.ai/code/session_01JCF8gyb8jNRmHmWqQmVhRJ


Generated by Claude Code

dry and others added 2 commits October 6, 2026 19:16
Not for merging. Tries the packages API with the fil-forge-bot token
promote-staging.sh uses, the same app token asking for packages read,
and the workflow's own token, looking up dev's pinned digests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JCF8gyb8jNRmHmWqQmVhRJ
@Peeja Peeja closed this Oct 7, 2026
@Peeja
Peeja deleted the claude/happy-bell-cfh5qb-packages-probe branch October 7, 2026 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant