Prepare release v5.0.0

[klediouron]

chore(merge main): patched commit → bf09367

• 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
  • if bumping a minor or major version:
    • Manually change version_short in package.json
    • Add docs version to _data/docs-versions.yml
    • Manually change docs_version in _config.yml
    • Update redirects in docs frontmatter
    • Move docs to the new docs' subfolder?
    • Ensure Algolia indexes new release content (probably requires a PR)
  • check wrong matches in CHANGELOG.md, and maybe site/content/docs/<version>/migration.md
• npm run release to compile dist, 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
• merge (on v5-dev for now)
• tag your version, and push your tag
• create a GitHub release:
  • attach zip file
  • paste CHANGELOG / Ship list in the release's description
• publish documentation on gh-pages:
  • copy ../bs-docs to the gh-pages branch
  • 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
• npm pack then npm publish
  • if you are already logged in NPM (with a personnal account, for example), you'd better use a repository scoped .npmrc file
  • if you're releasing a pre-release, use --tag, eg for v5-alpha1 npm publish boosted-5.0.0-alpha1.tgz --tag next
• publish on Nuget
• check release on NPM, Nuget, Packagist…
• make an announcement in Plazza 🎉

[klediouron]

Opened a PR for DocSearch config

[ffoodd]

Seems very good to me, only a few tweaks here and there 👌

[ffoodd]

Well done, keep going with DoD 😉

[ffoodd]

Why only hide it? Couldn't you replace SVG content with Orange's logo?
Didn't check at all where this is used, BTW :')

[Lausselloic]

display none move to svg itself

[ffoodd]

Hum so you did remove them. However they're probably called somewhere with the <use> tag and symbols' id, aren't they?

[Lausselloic]

yes ;-)

[ffoodd]

Going this way, you should probably use functional colors above too instead of supporting ones, isn't it?
Or does inconsistency acceptable here?

Definitely a topic to address wth the brand team, giving a red supporting color instead of the functional one, IMHO.

[klediouron]

Created an issue to keep track of this

[ffoodd]

If docs are using bundled JS, why do we use this? In "Getting Started" docs, maybe?

[Lausselloic]

Yes you're the author of the callout in introduction. In case project don't use boosted JS

{{< callout warning >}}
#### Required script

Boosted includes [WICG's `:focus-visible` polyfill](https://github.com/WICG/focus-visible) to ensure an enhanced focus visibility for keyboard users while shutting down focus styles on active state.
However, if you don't need or want to use Boosted's JavaScript files, you'll still need to use the polyfill.
```html
<script src="{{< param "cdn.focus_visible" >}}" integrity="{{< param "cdn.focus_visible_hash" >}}" crossorigin="anonymous"></script>

{{< /callout >}}

[klediouron]

It is used in Getting Started docs indeed:

<script src="{{< param "cdn.focus_visible" >}}" integrity="{{< param "cdn.focus_visible_hash" >}}" crossorigin="anonymous"></script>```