Skip to content

ci(release): publish from a separate job so failed publishes can be re-run - #21

Merged
ozandogrultan merged 2 commits into
mainfrom
ci/release-publish-job
Nov 8, 2026
Merged

ozandogrultan merged 2 commits into
mainfrom
ci/release-publish-job

Conversation

@ozandogrultan

Copy link
Copy Markdown
Owner

Summary

Splits release.yml into a cut job (bump, changelog, commit, tag, push) and a shared publish job. publish runs for v* tag pushes and after a successful cut, checks out the tag, and keeps the existing safety checks: tag matches package version, skip if already on npm, edit the release if it already exists.

If publishing fails, Re-run failed jobs retries only publish at the existing tag. Today, a rerun re-cuts from main, finds no notable commits and never publishes. RELEASING.md documents the retry.

The same file now goes into ghost, ember, sesh and quill. The only difference is sesh's apt step that installs its test tools. The workflow filename is unchanged, so the npm trusted-publisher settings still apply.

Type of change

  • Bug fix
  • New feature
  • Documentation
  • Refactor / internal

Checklist

  • bun run test passes.
  • bun run typecheck passes.
  • bun run lint:sh and bash scripts/changelog.sh check pass.
  • Read the "Caveats" section of the README; this change does not regress the
    prompt.footer composer marker, placeholder ownership or scoped accept-key behaviour.
  • I updated the docs where behaviour changed; released changelog entries remain unchanged.

…e-run

The cut job now only bumps, tags and pushes. A shared publish job runs for
tag pushes and after a cut, so Re-run failed jobs retries the existing tag.
Aligns release.yml across the opencode-* repos.
cut gets contents: write only; publish adds id-token: write and checks out
refs/tags/<tag> without persisted credentials. The tag push is atomic and
expression values reach run blocks through env.
@ozandogrultan
ozandogrultan merged commit 9dc4aeb into main Nov 8, 2026
8 checks passed
@ozandogrultan
ozandogrultan deleted the ci/release-publish-job branch November 8, 2026 11:46
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