feat(release): enable npm trusted packages #350
Merged
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 introduces several improvements to the release process, dependency management, and CI/CD workflows for the
@labdigital/commercetools-mockpackage. The main goals are to enhance security, ensure compatibility with newer Node.js versions, and adopt trusted publishing practices.Release Process & Security Improvements:
.github/workflows/ci-cd.yaml,package.json). [1] [2] [3] [4]package.json). [1] [2]CI/CD Workflow Enhancements:
.github/workflows/ci-cd.yaml).id-tokenandcontentsin the publish job to support trusted publishing (.github/workflows/ci-cd.yaml).NPM_CONFIG_PROVENANCEtotrueand removed the use ofNPM_TOKENfor publishing, aligning with trusted publishing requirements (.github/workflows/ci-cd.yaml).pnpm Workspace Configuration:
pnpm-workspace.yamlto enforce a minimum release age, trust policy, and specify only built dependencies.