feat(release): scope package to @kamansoft org and fix CI/CD pipeline#8
Merged
Conversation
- Rename package to @kamansoft/vite-plugin-flatwave-react (npm org scope) - Update all internal references: e2e tests, example workspace, vite.config - Fix release.yml: add CI prerequisite job, concurrency guard, npm upgrade to latest (required for OIDC), remove conflicting registry-url from setup-node, wire NPM_TOKEN to @semantic-release/npm - Fix ci.yml: remove redundant push-to-main trigger (release.yml re-runs CI internally before releasing) - Package @kamansoft/vite-plugin-flatwave-react@0.1.0 published to npm
Contributor
|
🎉 This PR is included in version 1.1.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.
Summary
This PR fixes the release automation end-to-end and publishes the package for the first time.
Changes
Package rename
vite-plugin-flatwave-react→@kamansoft/vite-plugin-flatwave-react(npm org scope)package.jsondependency key, examplevite.config.tsimport@kamansoft/vite-plugin-flatwave-react@0.1.0is live on npmjs.comrelease.yml— root-cause fixesNPM_TOKENwas in GitHub secrets but never passed to semantic-releaseNPM_TOKEN: ${{ secrets.NPM_TOKEN }}to the Release step envregistry-urlinsetup-nodecreated an.npmrcthat conflicted with@semantic-release/npm's own auth, causingEINVALIDNPMTOKENerrorsregistry-urlfromsetup-nodecijob as a prerequisite;releasejob only runs after CI passesconcurrencygroupnpm install -g npm@lateststepci.ymlpush: branches: [main]trigger —release.ymlruns its own CI gate, so CI was running twice on every mergeWhat happens after this merges
Releaseworkflow runs onpush: branches: [main]CI Validationjob runs first (full build + test suite)Release & Publish to npmjob runsnpx semantic-release@kamansoft/vite-plugin-flatwave-reactto npmjs, creates a GitHub ReleaseOptional upgrade (after merge): npm OIDC trusted publishing
Once the trusted publisher is configured on npmjs.com,
NPM_TOKENcan be removed from the workflow — OIDC handles auth automatically. Seedocs/ci-cd-release-automation.md(added in a follow-up) for instructions.