For the love of
semver
by Troy Rhinehart
semver
-
semver
-
pubish
-
deploy
semver
Semantic Versioning
a simple set of rules and requirements that dictate how version numbers are assigned and incremented
semver
Major
1
Breaking Change
Minor
2
New Feature
Patch
3
Bugs/Docs/Tests
(>= v1.0.0)
semver
Major
0
Breaking Change
Minor
1
Breaking Change
Patch
2
New Features AND Bugs/Docs/Tests
(< v1.0.0)
semver
semver
Ranges
| Symbol | Example | Description |
|---|---|---|
| * | "*" | Any/Latest |
| x | "0.0.x", "1.0.x", "1.x.x" | Any/Latest of position |
| ^ | "^0.6.0", "^15.3.0" | >=1 Minor/Patch, <1 Patch |
| ~ | "~0.3.0", "~3.3.0" | Patch |
semver
^1.2.3
| 0.5.0 | 1.2.3 |
| 1.3.4 | 2.0.0 |
semver
~1.2.3
| 0.5.0 | 1.2.2 |
| 1.3.4 | 1.2.6 |
semver
^0.6.2
| 0.5.0 | 1.0.0 |
| 0.6.6 | 0.7.0 |
make publicly known, reveal, divulge, announce
publish
publish
- Switch to master branch
- Delete node_modules
- Run install
- Run version bump
- Run publish
- Finally push
git checkout master
git pull rm -f node_modules npm install npm version major|minor|patch npm publish git push origin master
git push origin master --tagsto come into a position ready for use
deploy
deploy
- vnext-api
- vnext-editor
- onboarding
- more? 24
deploy
Onboarding
- Checkout branch
- Delete node_modules
- Run install
- Install with save flag
- Commit and push
- Create PR
git checkout -b <branch> rm -rf node_modules npm install npm i <name>@<version> -S|-D git commit -a -m "shrinkwrap"
git push -u origin <branch>/compare/<branch>
deploy
Editor/API
- Checkout branch
- Delete node_modules
- Run install
- Install with save flag
- Run shrinkwrap format
- Commit and push
- Create PR
git checkout -b <branch> rm -rf node_modules npm install npm i <name>@<version> -S|-D git commit -a -m "shrinkwrap"
git push -u origin <branch>/compare/<branch>
npm run shrinkwrapper-formatQuestions?
