Skip to content

Instantly share code, notes, and snippets.

@patrickkettner

patrickkettner/release_steps.md

Last active May 24, 2017 05:34
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save patrickkettner/9695bda2469b21b8d3332ec93e914206 to your computer and use it in GitHub Desktop.
Save patrickkettner/9695bda2469b21b8d3332ec93e914206 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
release_steps.md

release modernizr in 10 easy steps

  1. compare HEAD with most recent release to determine new semver level (fundemental/breaking changes = bump major, new feature-detects/publically-exposed-util = bump minor, update to existing code (in non behavior changing way) = bump patch). Github compare view is handy here (e.g. https://github.com/Modernizr/Modernizr/compare/v3.3.1...master)
  2. update package.json version to new semver version
  3. run git tag ${semver} (e.g. git tag v3.4.0), then push the tags (git push --tags)
  4. npm publish
  5. log into the modernizr.com server
  6. cd ~/modernizr-neue
  7. npm update && bower update
  8. npm run deploy
  9. pm2 restart 0
  10. write blog post explaining what has changed between versions
@ryanseddon
Copy link

nice I like to use npm version [major/minor/patch] -m "what changed" could work in this flow too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment