feat(release): enable npm trusted packages#350
Merged
mvantellingen merged 5 commits intomainfrom Nov 30, 2025
Merged
Conversation
🦋 Changeset detectedLatest commit: 9fb9f0e The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
mvantellingen
force-pushed
the
feature/trusted-packages
branch
from
f3819af to
79a78f1
Compare
mvantellingen
force-pushed
the
feature/trusted-packages
branch
2 times, most recently
from
0bb27a1 to
d425b43
Compare
Replace the `~src/` with node’s native subpath alias `#src/`
mvantellingen
force-pushed
the
feature/trusted-packages
branch
from
d425b43 to
9fb9f0e
Compare
Merged
mvantellingen
pushed a commit
that referenced
this pull request
Nov 30, 2025
This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## @labdigital/commercetools-mock@2.61.0 ### Minor Changes - [#347](#347) [`c7683d2`](c7683d2) Thanks [@tleguijt](https://github.com/tleguijt)! - Add removeQuantity action for inventory entries ### Patch Changes - [#350](#350) [`cfbc4ac`](cfbc4ac) Thanks [@mvantellingen](https://github.com/mvantellingen)! - Update release process to use trusted publishing - [#352](#352) [`93cebc5`](93cebc5) Thanks [@mvantellingen](https://github.com/mvantellingen)! - Update build process for the docker version - [#350](#350) [`cfbc4ac`](cfbc4ac) Thanks [@mvantellingen](https://github.com/mvantellingen)! - update various depdendencies to resolve potential security issues Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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 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.