Skip to content

Commit 8a7cc7c

Browse files
committed
fix: rename the 'publish' custom script to 'release'
As detailed in the NP (library that helps for the releases) readme, the custom script name shouldn't be `publish` (because it's an internal `npm` defined script). cf https://github.com/sindresorhus/np#release-script I always had the publishing script that got stuck right before pushing the git tag and never understood why. Now that it's fixed I get it... If only I had searched for this before 😅. Anyway no more manual git push tag for the next releases, just use `npm run release` ☺️🎉. I've updated the #18 issue which describes the release process.
1 parent a4f59c0 commit 8a7cc7c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

package.json

+1-1
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@
7373
"postpack": "rm -f oclif.manifest.json",
7474
"prepack": "rm -rf lib && npm run build && oclif-dev manifest && oclif-dev readme",
7575
"pretest": "npm run clean && npm run build && npm run lint",
76-
"publish": "np --no-release-draft",
76+
"release": "np --no-release-draft",
7777
"test": "mocha \"test/**/*.test.ts\"",
7878
"test-coverage": "nyc npm run test",
7979
"test-integration": "node ./test/integration.js",

0 commit comments

Comments
 (0)