Fix CLI release workflow after npm publish #283

New issue

Closed

opened 2026-05-11 15:40:11 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-11 15:40:11 +00:00

Owner

Problem

The cli-v0.0.5 workflow successfully published @barrettruth/delta@0.0.5 to npm, but the Forgejo Actions run still ended in failure after publish. The Forgejo release object was missing and had to be created manually with the published npm tarball asset.

Evidence

npm contains @barrettruth/delta@0.0.5.
Forgejo run 2609 / actions run 58 failed after about 85 seconds.
cli-v0.0.5 release was manually created after the workflow failure.

Acceptance criteria

Determine whether the failure is in tea login add, tea releases delete, or tea releases create.
Make future CLI tag releases end green after npm publish.
Keep the npm publish idempotency check intact.
Avoid printing or persisting any secret values in logs.

## Problem The `cli-v0.0.5` workflow successfully published `@barrettruth/delta@0.0.5` to npm, but the Forgejo Actions run still ended in failure after publish. The Forgejo release object was missing and had to be created manually with the published npm tarball asset. ## Evidence - npm contains `@barrettruth/delta@0.0.5`. - Forgejo run `2609` / actions run `58` failed after about 85 seconds. - `cli-v0.0.5` release was manually created after the workflow failure. ## Acceptance criteria - Determine whether the failure is in `tea login add`, `tea releases delete`, or `tea releases create`. - Make future CLI tag releases end green after npm publish. - Keep the npm publish idempotency check intact. - Avoid printing or persisting any secret values in logs.

barrettruth added the

track:infra

type:release

labels

2026-05-11 15:40:11 +00:00

barrettruth referenced this issue from a pull request that will close it,

2026-05-11 15:43:21 +00:00

Add Forgejo CLI to release shell #284

barrettruth closed this issue

2026-05-11 15:45:02 +00:00

barrettruth referenced this issue from a commit

2026-05-11 15:45:04 +00:00