ci: pin @sebbo2002/semantic-release-jsr to 3.2.1#92
Merged
Conversation
KyleJune
force-pushed
the
ci/pin-release-toolchain
branch
from
9e2761c to
8e09de4
Compare
4.0.0 ships a CJS bundle that semantic-release rejects as an invalid plugin config (EPLUGINSCONF), failing every Release job. Root cause is upstream issue #153: the v4 build tags module.exports with Symbol.toStringTag="Module", tripping semantic-release's isPlainObject() check. It's fixed on @next (4.0.1-develop) but not yet in a stable release, so the floating "latest" is still the broken 4.0.0. Pin only this plugin to the last working 3.x; the other five tools keep tracking latest. Un-pin to ^4.0.1 once it ships stable. Verified locally: with jsr 3.2.1 every plugin loads; swapping only jsr to 4.0.0 reproduces EPLUGINSCONF. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
KyleJune
changed the title
|
🎉 This PR is included in version 0.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Release job has failed on every push to
mainsince run 27482917285:Root cause
The
npxcommand pins no versions, so each--packagefloats to its latest.@sebbo2002/semantic-release-jsrpublished 4.0.0 the day after our last release, and its new CJS bundle tagsmodule.exportswithSymbol.toStringTag = "Module". semantic-release loads a plugin by importing that CJS entry and requires the result to be a plain object (lodash.isPlainObject) — aModule-tagged object fails the check, so the whole config is rejected.This is purely the plugin's build output (not a config error): with
semantic-releaseheld constant, jsr3.2.1loads fine and only jsr4.0.0reproduces the error.Tracked upstream in sebbo2002/semantic-release-jsr#153, already fixed on
@next(4.0.1-develop) — but not yet in a stable release, so floatinglatestis still the broken4.0.0.Fix
Pin only
@sebbo2002/semantic-release-jsrto3.2.1(the last working release). The other five tools keep tracking latest.4.0.0shipped no features (it only dropped Node 20 support), so nothing is lost by staying on 3.x.Follow-up: un-pin to
^4.0.1once it's released stable.Verified locally with
semantic-release --dry-run --no-ci: every plugin loads on3.2.1; swapping only jsr to4.0.0reproducesEPLUGINSCONF.🤖 Generated with Claude Code