fix(deps): carry semantic-release-config 1.2.3 into the release images

ryangr0 commented

2026-08-28 04:36:21 +00:00

Owner

Follow-up to PR #131. Config 1.2.3 (released from semantic-release-config PR #10) adds the load-time toolchain guard and the chore(deps) release-veto fix; this bakes it into all three images. Lockfiles verified: config 1.2.3, generator 15.0.0-beta.2 flat, no nested copies. Typed fix (not chore(deps)) because the pipeline cutting these image releases still runs the veto bug.

ryangr0 added 1 commit

2026-08-28 04:36:21 +00:00

fix(deps): carry semantic-release-config 1.2.3 into the release images cc9b75a8b7

1.2.3 adds the load-time toolchain guard (an incompatible notes generator now
fails the release loudly instead of shipping heading-only notes) and drops
the release:false rules that vetoed chore(deps)/build(deps) releases. The
1.2.2 in the current images already renders notes correctly via the image
manifests' own overrides; this bump makes the guard and the rules fix part
of the baked toolchain too.

Typed fix rather than chore(deps) deliberately: these images still release
through a toolchain carrying the veto bug, where a chore(deps) commit would
not cut a release at all.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

ryangr0 added 1 commit

2026-08-28 04:56:46 +00:00

fix: alpine toolchain images ship no bash — every composite step declares shell: bash 299537ea5a

The ADR-0006 Stage 2 move to the DHI node alpine base (v0.2.0/v0.3.0) kept
the builds green but no consumer ever ran those images: ploeg stayed pinned
to 0.1.2, the last debian image. The first real job on 0.3.1 (ploeg runs 226
and 227) died within seconds on its first `shell: bash` step — the base
ships only busybox sh, and the apk line installed git/ca-certificates/curl
but not bash. The rust image is untouched: it is still debian-based, where
bash is essential.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

ryangr0 added 1 commit

2026-08-28 05:00:19 +00:00

test(images): prove the runtime contract at build time — bash, bin, git preflight

[Workflow] On Source Change / Plan: guards + changed images + release matrix (push) Successful in 3s

Details

[Workflow] On Source Change / Build check (semantic-release, ops/docker/semantic-release) (push) Has been skipped

Details

[Workflow] On Source Change / Build check (semantic-release-monorepo, ops/docker/semantic-release-monorepo) (push) Has been skipped

Details

[Workflow] On Source Change / Build check (semantic-release-rust, ops/docker/semantic-release-rust) (push) Has been skipped

Details

[Workflow] On Source Change / Release (semantic-release, ops/docker/semantic-release) (push) Successful in 1m47s

Details

[Workflow] On Source Change / Release (semantic-release-monorepo, ops/docker/semantic-release-monorepo) (push) Successful in 2m10s

Details

[Workflow] On Source Change / Release (semantic-release-rust, ops/docker/semantic-release-rust) (push) Has been cancelled

Details

22731a944d

The node-side contract check verifies resolution but not execution: the
alpine wave (v0.2.0/v0.3.0) passed it while shipping no bash, and no
consumer ran those images until ploeg's first job on 0.3.1 died on its first
`shell: bash` step. The build now also executes the semantic-release bin
through bash, which additionally exercises its git preflight. An image that
cannot run the toolchain no longer builds.

The --version output is the image's own version, not 25.x — yargs resolves
the nearest package.json above its install dir, which is the root manifest
deliberately named after the image. Annotated in place; the node check above
asserts the real major.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

[Workflow] On Source Change / Plan: guards + changed images + release matrix (push) Successful in 3s

Details

[Workflow] On Source Change / Build check (semantic-release, ops/docker/semantic-release) (push) Has been skipped

Details

[Workflow] On Source Change / Build check (semantic-release-monorepo, ops/docker/semantic-release-monorepo) (push) Has been skipped

Details

[Workflow] On Source Change / Build check (semantic-release-rust, ops/docker/semantic-release-rust) (push) Has been skipped

Details

[Workflow] On Source Change / Release (semantic-release, ops/docker/semantic-release) (push) Successful in 1m47s

Details

[Workflow] On Source Change / Release (semantic-release-monorepo, ops/docker/semantic-release-monorepo) (push) Successful in 2m10s

Details

[Workflow] On Source Change / Release (semantic-release-rust, ops/docker/semantic-release-rust) (push) Has been cancelled

Details

This branch is already included in the target branch. There is nothing to merge.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin +refs/pull/132/head:ryangr0/fix/semrel-images-config-123

git switch ryangr0/fix/semrel-images-config-123

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main

git merge --no-ff ryangr0/fix/semrel-images-config-123

git switch ryangr0/fix/semrel-images-config-123

git rebase main

git switch main

git merge --ff-only ryangr0/fix/semrel-images-config-123

git switch ryangr0/fix/semrel-images-config-123

git rebase main

git switch main

git merge --no-ff ryangr0/fix/semrel-images-config-123

git switch main

git merge --squash ryangr0/fix/semrel-images-config-123

git switch main

git merge --ff-only ryangr0/fix/semrel-images-config-123

git switch main

git merge ryangr0/fix/semrel-images-config-123

git push origin main

Rows
Columns

fix(deps): carry semantic-release-config 1.2.3 into the release images #132

Checkout

Merge