We strongly encourage you to review the project's scope described in the README.md
file before working on new features. For large changes, consider writing a design document using this template.
Start from a clean checkout at master/HEAD. Check if there are any breaking changes since the last tag - if so, this will be a minor, if not, it's a patch. (This may not sound like semver - but since our major version is a zero, the rule is that minors are breaking changes and patches are new features).
yarn skydoc
bazel run :gazelle
check_rules_nodejs_version
in ts_repositories.bzl
git commit -a -m 'Update docs for release'
npm config set tag-version-prefix ''
npm version minor -m 'rel: %s'
(replace minor
with patch
if no breaking changes)bazel run //internal:npm_package.publish && bazel run //internal/karma:npm_package.publish
bazel build :release
git push && git push --tags
bazel-bin/release.tgz
file