[TEST]

[julien-deramond]

• 2177
• Run linters;
• Run compilers;
• Run tests;
• Check documentation site: examples and contents;
• Test cross-browser compatibility locally and with BrowserStack:
• Firefox ESR
• IE11 (v4 only)
• Latest Edge, Chrome, Firefox, Safari
• iOS Safari
• Chrome & Firefox on Android
• Including RTL mode;
• Ask for reviews and accessibility testing;
• sync with Bootstrap's release and probably wait for it;
• npm run release-version $current_version $next_version to bump version number
• then, if bumping a minor or major version:
• Manually change version_short in package.json
• Add docs version to site/data/docs-versions.yml
• Manually change docs_version in hugo.yml and other references to the previous version
• Update redirects in docs frontmatter (site/content/docs/_index.html?)
• Move site/content/docs/5.x to site/content/docs/5.x+1
• Increment site/static/docs/{version} version
• Increment version in nuget/boosted.nuspec
• (Major version) Manually update the version in nuget/boosted.nuspec and nuget/boosted.sass.nuspec
• check wrong matches in CHANGELOG.md, and maybe site/content/docs/<version>/migration.md
• ⚠️ check the package-lock.json and package.json content, only "boosted" should have its version changed!
• ⚠️ site/content/docs/5.1/**/*.md should not always be modified
• if year changed recently, happy new year 🎉 but please change © year in .scss main files (reboot, grid, utilities and main file) as well as in NOTICE.txt.
• npm run release to compile dist, build Storybook, update SRI hashes in doc and package the release
• Prepare changelog:
• install Conventionnal Changelog and conventional-changelog-cli globally
• run conventional-changelog -p angular -i CHANGELOG.md -s
• and probably maintain a ship list (eg for v4.4.0)
• 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:
• attach zip file
• paste CHANGELOG / Ship list in the release's description
• Pack and publish
• npm pack
• if you are already logged in NPM (with a personnal account, for example), you'd better use a repository scoped .npmrc file
• Publish:
• if you're releasing a pre-release, use --tag, eg 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 boosted@5.x.y latest to fix it)
• (v5 only) npm publish
• publish on Nuget
• check release on NPM, Nuget, Packagist…
• 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 be redirecting 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 occurences
• make an announcement in GitHub Discussions and internal communication channels 🎉

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	8642df5
🔍 Latest deploy log	https://app.netlify.com/sites/boosted/deploys/64c11e7a550d0200087c0412
😎 Deploy Preview	https://deploy-preview-2177--boosted.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	31ba4c1
🔍 Latest deploy log	https://app.netlify.com/sites/boosted/deploys/64c11eaf2f4a5900087dddfa
😎 Deploy Preview	https://deploy-preview-2177--boosted.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.