|
4 | 4 | - then, if bumping a minor or major version: |
5 | 5 | - [ ] Manually search and replace `$current_version` in all files, meaning changes should happen in: |
6 | 6 | - [ ] The style sheet loaded in `.storybook/preview-head.html` |
7 | | - - [ ] Some download links in the `README.md` |
8 | 7 | - [ ] `docs_version` in `config.yml` and other references to the previous version |
9 | | - - [ ] `VERSION` in `js/src/base-component.js` |
10 | | - - [ ] `version_short` in `package.json` |
11 | | - - [ ] `scss/mixins/_banner.scss` |
| 8 | + - [ ] Update the pixel tracker URL in all `packages/**/scss/_composite.scss` |
12 | 9 | - [ ] `scss/docs.scss` |
13 | 10 | - [ ] Several markdown files and markdown extended files |
14 | 11 | - [ ] Add docs version to `site/data/docs-versions.yml` |
15 | | - - [ ] Update the home news for the next release |
16 | | - - [ ] Move `site/content/docs/x.y` to `site/content/docs/x.y+1` |
17 | | - - [ ] Move `site/static/docs/x.y` to `site/static/docs/x.y+1` |
18 | | - - [ ] Make sure the migration guide is updated only for the next version |
19 | | - - [ ] (Major version) Manually update the version in `nuget/ouds-web.nuspec` and `nuget/ouds-web.sass.nuspec` |
20 | 12 | - [ ] Check that the changes in the migration guide only apply to the latest version |
| 13 | + - [ ] (Major version) Manually update the version in `nuget/ouds-web.nuspec` and `nuget/ouds-web.sass.nuspec` |
| 14 | + - [ ] Update the home news for the next release |
21 | 15 | - check wrong matches in `CHANGELOG.md`, and maybe `site/content/docs/<version>/migration.md` |
22 | 16 | - :warning: check the `package-lock.json` and `package.json` content, only "@ouds/web" should have its version changed! |
23 | 17 | - [ ] if the year changed recently, happy new year :tada: but please change © year in `.scss` main files (reboot, grid, utilities, and main file) as well as in `NOTICE.txt`. |
|
28 | 22 | - [ ] Make sure to import all the bad named commits |
29 | 23 | - [ ] Commit and push `dist` with a `chore(release): vx.y.z` commit message |
30 | 24 | - [ ] Merge on `ouds/main` |
31 | | -- [ ] Tag your version, and push your tag using `git tag vx.y.z-ouds-web` and `git push vx.y.z-ouds-web` |
32 | | -- [ ] Pack and publish |
33 | | - - `npm pack` |
| 25 | +- [ ] Tag your version, and push your tag using `git tag -s vx.y.z-ouds-web` and `git push origin vx.y.z-ouds-web` |
| 26 | +- [ ] Pack and publish for the common part and all the brands |
| 27 | + - `npm run pack` |
34 | 28 | - 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) |
35 | 29 | - Publish: |
36 | 30 | - if you're releasing a pre-release, use `--tag`, e.g. for v1-alpha1 `npm publish ouds-web-1.0.0-alpha1.tgz --tag next` |
37 | | - - `npm publish` |
38 | | - <!-- When there is several branches to maintain |
39 | | - - (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 boosted@5.x.y latest` to fix it) --> |
| 31 | + - `npm run publish` |
40 | 32 | - [ ] check release on [NPM](https://www.npmjs.com/package/@ouds/web), [Nuget](https://www.nuget.org/packages/@ouds/web/), [Packagist](https://packagist.org/packages/orange-opensource/orange-boosted-bootstrap)… |
41 | 33 | - [ ] publish documentation on `main` of the [ouds-web-doc](https://github.com/Orange-OpenSource/ouds-web-doc) repo: |
42 | | - - [ ] copy `../_site` to the `main` branch |
43 | | - - [ ] don't forget to update Storybook as well and double-check that pages are referenced |
44 | | - - [ ] check every `index.html` used as redirections to redirect to the new release |
| 34 | + - [ ] run `npm run storybook-build` from `Orange-Boosted-Bootstrap` (be careful that `release-sri` doesn't update `config.yml`s) |
| 35 | + - [ ] remove `storybook` folder from `ouds-web-doc` |
| 36 | + - [ ] copy `Orange-Boosted-Bootstrap/_site` to a new branch starting from `ouds-web-doc#main` |
| 37 | + - [ ] check every `index.html` used as redirection, redirect to the new release |
45 | 38 | - [ ] when bumping minor or major version: ensure `dist` URLs in examples' HTML has changed |
46 | 39 | - [ ] double-check everything before pushing, starting by searching for forgotten old version number occurrences |
47 | | - - [ ] Make the new release banner appears in the previous version of the doc (e.g. in v5.3 when releasing the v5.4.0 doc) |
48 | | -<!-- When there is a v1 released |
49 | | -- [ ] make an announcement in [GitHub Discussions](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/discussions/categories/announcements) (+ pin the new GH Discussion) --> |
| 40 | + - [ ] Make the new release banner appears in the previous version of the doc (e.g. in v5.3 when releasing the v5.4.0 doc, search for `navbar navbar-expand supra d-none` and replace by `navbar navbar-expand supra`) |
| 41 | + - [ ] Make the new release remove the Netlify badge in the newly released version of the documentation (search for `Netlify` and remove the badge in the new release) |
| 42 | +- [ ] Run Algolia crawler manually for the new documentation to be indexed in the search engine (https://dashboard.algolia.com/apps/AKIHKMSEKB/dashboard) |
50 | 43 | - [ ] [create a GitHub release](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/releases/new): |
51 | | - - attach the 2 zip files |
| 44 | + - attach the 2 zip files per brand |
52 | 45 | - paste the CHANGELOG / Ship list in the release's description |
53 | | -<!-- When there is a v1 released |
54 | | -- [ ] make an announcement on internal communication channels :tada: --> |
| 46 | +- [ ] make an announcement in [GitHub Discussions](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/discussions/categories/announcements) (+ pin the new GH Discussion) |
| 47 | +- [ ] make an announcement on internal communication channels and publish posts :tada: |
55 | 48 | - [ ] [publish on Nuget](https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/wiki/Generate-NuGet-packages) |
0 commit comments