Releasing
- Core
- Optional
- Tooling
Releasing new builds of mithril is mostly automated via npm version
Publishing to NPM
npm version <major|minor|patch|semver> -m "v%s"
All further steps are automated and run as follows:
- Tests are run
- Linting is run (but doesn't fail build)
- Version number in package.json is incremented
- New bundles are generated using updated version
git add
called on bundle outputpackage.json
and updated bundles are committed to git- previous commit is tagged using new version number
git push --follow-tags
pushes up new version commit & tag to github- Travis sees new release, starts build
- Travis generates new bundles before running tests
- Travis runs tests
- Travis lints files (but can't fail build)
- If build fails, abort
- Build succeeded, so travis will commit back any changes to the repo (but there won't be any)
- Travis sees that this commit has a tag associated with it
- Travis will use the encrypted npm creds in
.travis.yml
to publish a new version to npm
Publishing a GitHub release
TODO
Updating docs/change-log.md
TODO
License: MIT. © Leo Horie.