Update package.json to use preversion, version, and postversion
- Dominant language
- JavaScript
- Stars
- 441
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
Update package.json to use preversion, version, and postversion
Example: https://github.com/canjs/can-set/blob/master/package.json
``` javascript
//...
"scripts": {
"preversion": "npm test && npm run build",
"version": "git commit -am \"Update dist for release\" && git checkout -b release && git add -f dist/",
"postversion": "git push --tags && git checkout master && git branch -D release && git push",
"release:patch": "npm version patch && npm publish",
"release:minor": "npm version minor && npm publish",
"release:major": "npm version major && npm publish",
"jshint": "jshint src/. --config",
"testee": "testee test.html --browsers firefox",
"test": "npm run jshint && npm run testee",
"build": "node build.js"
},
//...
```
Contributor guide
Research direction
Start with package.json and compare its scripts with the can-set package.json example linked in the issue. Check how the existing test and build commands relate to the proposed preversion, version, postversion, and release scripts, including build.js. Done means package.json contains the requested release workflow and its commands are consistent with the repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100