chore: publish npm via DK-CICD instead of NPM_TOKEN - #58
Open
caroolcanelas2 wants to merge 1 commit into
Open
Conversation
The GitHub Actions NPM_TOKEN secret is expired, so tag publishes fail. Switch to the same npm-publish-v1 + Trusted Publishing flow used by node-vtex-api. Co-authored-by: Cursor <cursoragent@cursor.com>
|
0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage
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.
This pull request updates the CI/CD and npm publishing workflows to modernize and improve the release process. The main changes are the removal of legacy GitHub Actions workflows, the introduction of a new workflow leveraging AWS CodeArtifact and GitHub Trusted Publishing, and the integration of this workflow into the DK-CICD pipeline.
Publishing and CI/CD workflow updates:
publish-npm.yml, to publish packages from AWS CodeArtifact to npm using GitHub Trusted Publishing and environment-based tagging (production or beta). This workflow uses modern Node.js versions and improved credential management.publish-npm.ymlworkflow into the DK-CICD pipeline via thenpm-publish-v1step in.vtex/deployment.yaml, enabling publishing on tag push events.Removal of legacy workflows:
ci.yml) that handled linting and testing across platforms.publish-prerelease-npm.yml) and stable releases (publish-stable-npm.yml), which relied onNPM_TOKENand older Node.js versions. [1] [2]Documentation:
CHANGELOG.mdto reflect the switch to DK-CICD and GitHub Trusted Publishing for npm releases.The GitHub Actions NPM_TOKEN secret is expired, so tag publishes fail. Switch to the same npm-publish-v1 + Trusted Publishing flow used by node-vtex-api.