Conversation
There was a problem hiding this comment.
Pull request overview
This PR prepares a new version release by bumping the package version and updating the CI/CD publish workflow to ensure the latest npm tooling is used during the publishing process.
- Version bump from 2.1.13 to 2.1.14
- Added npm upgrade step in the publish workflow to ensure latest npm is used
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Bumps package version from 2.1.13 to 2.1.14 for new release |
| .github/workflows/publish.yml | Adds global npm upgrade to latest version before package installation and publishing |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| with: | ||
| node-version: 24 | ||
| registry-url: "https://registry.npmjs.org" | ||
| - run: npm install -g npm@latest |
There was a problem hiding this comment.
The npm install -g npm@latest step may introduce unpredictability in the CI/CD pipeline by installing whatever the latest npm version is at runtime. This could lead to inconsistent builds or unexpected breaking changes.
Consider pinning to a specific npm version (e.g., npm@10.x.x or npm@11.x.x) to ensure reproducible builds and avoid potential issues from future npm updates.
| - run: npm install -g npm@latest | |
| - run: npm install -g npm@10.5.0 |
1 participant
No description provided.