Closed MikeMcC399 closed 3 months ago
@MikeMcC399 Should this be tagged as a 'feat' for the example kitchensink?
@jennifer-shehane
Should this be tagged as a 'feat' for the example kitchensink?
Using the commit type feat
is a workaround.
chore(deps)
were used, then the change would not be tested, because there would be no release triggered.fix
or feat
fix(deps)
were used then the release would be labeled under "Bug fixes", which could be misleadingfeat(deps)
causes a release with minor version update. This tests the change by triggering a release and the label is "Features".I`ve used this method elsewhere and it seemed like the best compromise to achieve the desired result of testing the PR and producing a release which is least misleading.
:tada: This PR is included in version 3.1.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Issue
npm audit
reports 5 vulnerabilities (4 moderate, 1 high) due tosemantic-release@21.1.2
Background
semantic-release@22.0.0 requires Node.js >= v20.6.0 semantic-release@23.0.0 requires Node.js >= v20.8.1 semantic-release@24.0.0 has no change for Node.js, however it is currently using beta dependencies
Change
Update
package.json
to semantic-release@23.1.1 Runnpm audit fix
after update.Update the
release
job in .circleci/config.yml to usesemantic-release@23.1.1
and to run under Node.js20.13.1
.(Node.js
18.16.1
is not compatible with semantic-release@22.0.0 and above which requires a minimum of Node.js18.17.0
.)Verification
npm audit
should report