Skip to content

CI: manual publish-untested mode (publish a v* tag to beta without the sync test) - #269

Merged
5PK merged 1 commit into
mainfrom
ci-manual-publish
Nov 10, 2026
Merged

5PK merged 1 commit into
mainfrom
ci-manual-publish

Conversation

@5PK

@5PK 5PK commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

Adds a publish-untested mode to the Publish to npm workflow's "Run workflow" button, for when the dev instances the sync permutation test leases are down (the 1.3.1-beta.1/beta.2 gates failed on dev-server SQL timeouts, HTTP 503s and an empty target Fetch API, not on the CLI).

  • Inputs: mode (promote default, or publish-untested) and version.
  • publish-untested: must run from main; checks out the existing v<version> tag, checks package.json matches and that the version isn't already on npm, builds, runs the unit tests, publishes under beta, and notes the skipped sync test in the run summary.
  • In npm-publish.yml rather than a new file, because npm's trusted publisher only accepts publishes from this workflow.
  • promote is unchanged apart from its if.

First use: publish 1.3.1-beta.2 (tag on afc0049, #265–#268).

🤖 Generated with Claude Code

…the sync test

For when the dev instances the sync permutation test leases are down. Runs from
the Actions tab on main: checks out the existing tag, checks package.json and
that the version isn't already on npm, builds, runs the unit tests and
publishes under beta. In npm-publish.yml because npm's trusted publisher only
accepts publishes from that file. The promote mode is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@5PK
5PK merged commit 3ad392e into main Nov 10, 2026
3 checks passed
@5PK 5PK mentioned this pull request Nov 13, 2026
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