Skip to content

chore: merge dev into main - #12

Merged
TitusKirch merged 3 commits into
mainfrom
dev
Sep 1, 2026
Merged

TitusKirch merged 3 commits into
mainfrom
dev

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

Automated rollup PR for changes accumulated on dev. Mark ready when you want release-please to pick it up — and use a merge commit, not squash, so individual feat:/fix: commits stay visible to release-please.

The workflow had one job. It tagged, wrote the GitHub release, moved the
major alias — and stopped. Three tags exist that npm never saw; the only
published version came from a manual run.

Two pieces were missing. The job exposed no outputs, so nothing downstream
could learn whether a release happened: step outputs are invisible across
jobs. And there was no publish job to consume them.

dev now reaches the workflow for the prerelease job, with release-please
itself gated to the release branch, matching coverage-report.

scripts/backfill-npm.sh publishes the tags that were missed. It walks them
oldest-first under a throwaway dist-tag, because npm moves latest to whatever
went out last — an old version published after a new one would otherwise
become what npm install hands out.
Comment thread .github/workflows/release-please.yml Fixed
Comment thread .github/workflows/release-please.yml Fixed
A one-off for the three tags that were cut while release-please.yml had no
publish job. That gap is closed, so the script has nothing left to do.
@TitusKirch
TitusKirch marked this pull request as ready for review September 1, 2026 17:10
CodeQL flagged both publish jobs: a seven-character hash is not immutable
enough to be a pin, because an abbreviation can grow ambiguous as the
repository does. The full 40 characters cannot.
@TitusKirch
TitusKirch merged commit 34e5579 into main Sep 1, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants