chore: release @slack/[email protected]#2433
Conversation
| 3. Bump the version number in adherence to [Semantic Versioning](http://semver.org/) in `package.json`. (see [Versioning and Tags](https://github.com/slackapi/node-slack-sdk/blob/main/.github/maintainers_guide.md#versioning-and-tags)) | ||
| - The version must be in the format of `Major.Minor.Patch-BetaNamespace.BetaVersion` (ex: `5.10.0-workflowStepsBeta.1`, `2.5.0-rc.1`) | ||
| - Update any dependency versions in `package.json` and install locally `rm -rf node_modules && npm install` | ||
| - Update any dependency versions in `package.json` and install locally `rm -r node_modules package-lock.json && npm install` |
There was a problem hiding this comment.
-rf is not needed anymore?
There was a problem hiding this comment.
-r is to remove files in a directory recessively, -rf is to force remove files recessively, the force flag brings additional risk of accidentally deleting something important if you run this command in the wrong directory
There was a problem hiding this comment.
ahh yeah, I was wondering if users would run into permission errors with deleting if we had guidance to use -r only vs. -rf. but we can always add it back if needed! I agree to go with the less destructive command as guidance
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2433 +/- ##
=======================================
Coverage 92.59% 92.59%
=======================================
Files 36 36
Lines 7472 7472
Branches 653 653
=======================================
Hits 6919 6919
Misses 545 545
Partials 8 8 ☔ View full report in Codecov by Sentry. |
2 participants
Summary
Release @slack/[email protected]
Requirements