Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release instructions for @bazel/jasmine #552

Merged
merged 1 commit into from
Feb 18, 2019
Merged

Add release instructions for @bazel/jasmine #552

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions DEVELOPING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ Check if there are any breaking changes since the last tag - if so, this will be
1. `npm config set tag-version-prefix ''` (we don't put a "v" prefix on our tags)
1. `npm version minor -m 'rel: %s'` (replace `minor` with `patch` if no breaking changes)
1. `git push upstream && git push upstream --tags`
1. Build npm packages and publish them: TMP=$(mktemp -d -t bazel-release.XXXXXXX); ( cd packages/jasmine && bazel --output_base=$TMP run //:package.publish )
1. (Manual for now): go to the [releases] page, edit the release with rough changelog (especially note any breaking changes!) and upload the release artifact from `rules_nodejs-[version].tar.gz`
1. Announce the release on Angular slack in `#tools-abc-discuss`

Expand Down