-
Notifications
You must be signed in to change notification settings - Fork 54
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: enhance PR template for releases
- Loading branch information
1 parent
cde9c47
commit 929c007
Showing
1 changed file
with
9 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -110,27 +110,28 @@ _Note: Please transform `- [ ]` into `- (NA)` in the description when things are | |
| - install [Conventionnal Changelog](https://github.com/conventional-changelog/conventional-changelog) and `conventional-changelog-cli` globally | ||
| - run `conventional-changelog -p angular -i CHANGELOG.md -s` | ||
| - and probably maintain [a ship list (e.g. for v4.4.0)](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/issues/226) | ||
| - [ ] commit and push `dist` with a `chore(release)` commit message | ||
| - [ ] Commit and push `dist` with a `chore(release)` commit message | ||
| - [ ] Manually run BrowserStack test | ||
| - [ ] Manually run Percy test | ||
| - [ ] merge (on `v4-dev` or `main`) | ||
| - [ ] tag your version, and push your tag | ||
| - [ ] [create a GitHub release](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/releases/new): | ||
| - attach the zip file | ||
| - paste the CHANGELOG / Ship list in the release's description | ||
| - [ ] Merge (on `v4-dev` or `main`) | ||
| - [ ] Tag your version, and push your tag | ||
| - [ ] Pack and publish | ||
| - `npm pack` | ||
| - if you are already logged in to NPM (with a personal account, for example), [you'd better use a repository scoped `.npmrc` file](https://stackoverflow.com/questions/30114166/how-to-have-multiple-npm-users-set-up-locally) | ||
| - Publish: | ||
| - if you're releasing a pre-release, use `--tag`, e.g. for v5-alpha1 `npm publish boosted-5.0.0-alpha1.tgz --tag next` | ||
| - (v4 only) `npm publish --tag v4.x.y` (if you forgot and v4 becomes the latest version on NPM, you can run `npm dist-tag add [email protected] latest to fix it) | ||
| - (v5 only) `npm publish` | ||
| - [ ] [publish on Nuget](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/wiki/Generate-NuGet-packages) | ||
| - [ ] check release on [NPM](https://www.npmjs.com/package/boosted), [Nuget](https://www.nuget.org/packages/boosted/), [Packagist](https://packagist.org/packages/orange-opensource/orange-boosted-bootstrap)… | ||
| - [ ] publish documentation on `gh-pages`: | ||
| - [ ] copy `../_site` to the `gh-pages` branch (don't forget to update Storybook as well) | ||
| - [ ] check every `index.html` used as redirections to redirect to the new release | ||
| - [ ] when bumping minor version: ensure `dist` URLs in examples' HTML has changed | ||
| - [ ] double-check everything before pushing, starting by searching for forgotten old version number occurrences | ||
| - [ ] make an announcement in [GitHub Discussions](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/discussions/categories/announcements) (+ pin the new GH Discussion) and internal communication channels :tada: | ||
| - [ ] make an announcement in [GitHub Discussions](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/discussions/categories/announcements) (+ pin the new GH Discussion) | ||
| - [ ] [create a GitHub release](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/releases/new): | ||
| - attach the zip file | ||
| - paste the CHANGELOG / Ship list in the release's description | ||
| - [ ] make an announcement on internal communication channels :tada: | ||
| - [ ] [publish on Nuget](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/wiki/Generate-NuGet-packages) | ||
| --> | ||