ci: remove stale upstream publish.yml - #3
Merged
Conversation
The original upstream (andi23rosca) semantic-release publish workflow triggers on every push to main and now hard-fails at setup: pnpm/action-setup@v2 with `version: latest` resolves pnpm 11.x, which requires Node >= 22.13, while the workflow pins actions/setup-node@v3 to node 18. Every push to main therefore shows a red `Publish` check. The workflow is a stale artifact: it runs `npx semantic-release` against the old upstream config and could never publish the scoped `@rigelbuild/solid-markdown` package. It is not a required status context (the main ruleset gates on `CI` only), so the failure is cosmetic — but it reddens main on every push. The RIG-2187 react-markdown-10 fork PR supplies the replacement: a tag-driven, dist-tag-aware scoped publish workflow. Delete the stale one now so main is green; the replacement lands with that PR. Refs RIG-2187 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
marked this pull request as ready for review
August 21, 2026 22:09
mattwilkinsonn
approved these changes
Aug 22, 2026
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
2 participants
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.
The original upstream (andi23rosca) semantic-release publish workflow
triggers on every push to main and now hard-fails at setup: pnpm/action-setup@v2
with
version: latestresolves pnpm 11.x, which requires Node >= 22.13, whilethe workflow pins actions/setup-node@v3 to node 18. Every push to main therefore
shows a red
Publishcheck.The workflow is a stale artifact: it runs
npx semantic-releaseagainst the oldupstream config and could never publish the scoped
@rigelbuild/solid-markdownpackage. It is not a required status context (the main ruleset gates on
CIonly), so the failure is cosmetic — but it reddens main on every push.
The RIG-2187 react-markdown-10 fork PR supplies the replacement: a tag-driven,
dist-tag-aware scoped publish workflow. Delete the stale one now so main is
green; the replacement lands with that PR.
Refs RIG-2187
Co-authored-by: Matt Wilkinson matt@rigel.build