- FORGEJO_TOKEN is scoped as a step-level env var on both curl steps so the token isn't visible to other steps #7

Merged
longjacksonle merged 1 commit from long-msp-30 into main 2026-04-02 19:08:59 +02:00
Member
  • The Create release step captures release_id via jq --raw-output '.id' and writes it to GITHUB_OUTPUT so the
    Upload step can reference it as ${{ steps.create-release.outputs.release_id }}
  • The asset upload uses --form "attachment=@..." which is the correct multipart form field name for the
    Forgejo releases asset endpoint
  • --silent --show-error suppresses progress noise but keeps error messages, same pattern as the existing
    package registry upload in build-oci-image.yml
  • No shell: override needed — the runner's default bash handles both ${{ }} expansion and the curl commands
    correctly
- The Create release step captures release_id via jq --raw-output '.id' and writes it to GITHUB_OUTPUT so the Upload step can reference it as ${{ steps.create-release.outputs.release_id }} - The asset upload uses --form "attachment=@..." which is the correct multipart form field name for the Forgejo releases asset endpoint - --silent --show-error suppresses progress noise but keeps error messages, same pattern as the existing package registry upload in build-oci-image.yml - No shell: override needed — the runner's default bash handles both ${{ }} expansion and the curl commands correctly
- FORGEJO_TOKEN is scoped as a step-level env var on both curl steps so the token isn't visible to other steps
Some checks failed
Release / Build and release explorer-bookmarks binary (push) Failing after 1m15s
19d359c73b
- The Create release step captures release_id via jq --raw-output '.id' and writes it to GITHUB_OUTPUT so the
  Upload step can reference it as ${{ steps.create-release.outputs.release_id }}
  - The asset upload uses --form "attachment=@..." which is the correct multipart form field name for the
  Forgejo releases asset endpoint
  - --silent --show-error suppresses progress noise but keeps error messages, same pattern as the existing
  package registry upload in build-oci-image.yml
  - No shell: override needed — the runner's default bash handles both ${{ }} expansion and the curl commands
  correctly
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
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
pandoras-box/explorer-bookmarks!7
No description provided.