ci(release): drop legacy release.yml, trigger components release on workflow changes - #555
Merged
Merged
Conversation
…orkflow changes npm trusted publishing for @swr-data-lab/components now points at release-components.yml, so the old release.yml (kept only for the OIDC binding, see its TODO) would fail on every components push. release-components.yml now also runs when the workflow file itself changes, so edits to it are exercised on merge. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
romanlamsal
added a commit
that referenced
this pull request
Sep 30, 2026
semantic-release analyzed every commit since a package's last tag, regardless of which files it touched. The components-map fix in #554 therefore also released @swr-data-lab/components@4.0.1 when #555 triggered the components workflow. Both packages now extend semantic-release-monorepo, which limits analyzeCommits and generateNotes to commits that changed files inside the package folder. The explicit tagFormat keeps the existing components-v* / components-map-v* tags (the plugin's default would be @swr-data-lab/<pkg>-v*). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Sep 30, 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
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.
.github/workflows/release.yml. It only existed because npm trusted publishing for@swr-data-lab/componentswas bound to that filename (see its TODO); the trusted publisher now points atrelease-components.yml, so the old workflow would fail on everycomponents/**push..github/workflows/release-components.ymlto its ownpathstrigger, so changes to the workflow are exercised when merged.Expected on merge:
release componentsruns. semantic-release doesn't filter commits by path, so it will pick upfix(components-map): …(#554) sincecomponents-v4.0.0and publish@swr-data-lab/components@4.0.1(no code changes incomponents).🤖 Generated with Claude Code