- Two steps collapsed into one — RELEASE_ID is a plain shell variable in the same process, never touching #8

Merged
longjacksonle merged 1 commit from long-msp-30 into main 2026-04-02 19:26:19 +02:00
Member

GITHUB_OUTPUT. This eliminates the most likely failure: Forgejo runner not setting GITHUB_OUTPUT, or the
step-output read returning empty and silently posting to a bad URL.

  • TAG passed as an env var — ${{ forgejo.ref_name }} is expanded once at the YAML level into TAG, then used
    consistently across both curl calls as ${TAG}. Cleaner than mixing template expressions and shell variables in
    a single command.
  • echo "Created release ID: ${RELEASE_ID}" added — if jq returns null (meaning the create-release response was
    unexpected), this will print null visibly in the log before the upload curl fails with a 404, making the root
    cause obvious.
GITHUB_OUTPUT. This eliminates the most likely failure: Forgejo runner not setting GITHUB_OUTPUT, or the step-output read returning empty and silently posting to a bad URL. - TAG passed as an env var — ${{ forgejo.ref_name }} is expanded once at the YAML level into TAG, then used consistently across both curl calls as ${TAG}. Cleaner than mixing template expressions and shell variables in a single command. - echo "Created release ID: ${RELEASE_ID}" added — if jq returns null (meaning the create-release response was unexpected), this will print null visibly in the log before the upload curl fails with a 404, making the root cause obvious.
GITHUB_OUTPUT. This eliminates the most likely failure: Forgejo runner not setting GITHUB_OUTPUT, or the
  step-output read returning empty and silently posting to a bad URL.
  - TAG passed as an env var — ${{ forgejo.ref_name }} is expanded once at the YAML level into TAG, then used
  consistently across both curl calls as ${TAG}. Cleaner than mixing template expressions and shell variables in
   a single command.
  - echo "Created release ID: ${RELEASE_ID}" added — if jq returns null (meaning the create-release response was
   unexpected), this will print null visibly in the log before the upload curl fails with a 404, making the root
   cause obvious.
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!8
No description provided.