chore(release): v0.5.0

[louismaximepiton]

Release v0.5.0

• npm run release-version $current_version $next_version to bump version number
  • then, if bumping a minor or major version:
    • Manually search and replace $current_version in all files, meaning changes should happen in:
      • The style sheet loaded in .storybook/preview-head.html
      • Some download links in the README.md
      • docs_version in config.yml and other references to the previous version
      • VERSION in js/src/base-component.js
      • version in package.js
      • version_short in package.json
      • scss/mixins/_banner.scss
      • scss/docs.scss
      • Several markdown files
      • Add docs version to site/data/docs-versions.yml
      • Update the home news for the next release
      • (Major version) Manually update the version in nuget/ouds-web.nuspec and nuget/ouds-web.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 "@ouds/web" should have its version changed!
• if the 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 Conventional Changelog and conventional-changelog-cli globally
  • run conventional-changelog -p angular -i CHANGELOG.md -s
• Commit and push dist with a chore(release): vx.y.z commit message
• Merge on ouds/main
• Tag your version, and push your tag using git tag vx.y.z-ouds-web and git push vx.y.z-ouds-web
• 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
  • Publish:
    • 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
    • npm publish
• check release on NPM, Nuget, Packagist…
• publish documentation on main of the ouds-web-doc repo:
  • copy ../_site to the main 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 or major version: ensure dist URLs in examples' HTML has changed
  • double-check everything before pushing, starting by searching for forgotten old version number occurrences
  • Uncomment banner for previous version

• create a GitHub release:
  • attach the 2 zip files
  • paste the CHANGELOG / Ship list in the release's description

• publish on Nuget

[netlify]

✅ Deploy Preview for boosted ready!

Name	Link
🔨 Latest commit	10b026e
🔍 Latest deploy log	https://app.netlify.com/projects/boosted/deploys/686514dd266e790008aca523
😎 Deploy Preview	https://deploy-preview-3047--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 project configuration.

[MaxLardenois]

LGTM 🚀