Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 v5.2.1 #1568

Merged
merged 6 commits into from
Oct 31, 2022
Merged

🚀 v5.2.1 #1568

merged 6 commits into from
Oct 31, 2022

Conversation

julien-deramond
Copy link
Member

@julien-deramond julien-deramond commented Oct 24, 2022

Specific to this version

Generic

  • 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 config.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
      • Ensure Algolia indexes new release content (probably requires a PR)
      • (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, update SRI hashes in doc and package the release
  • Prepare changelog:
  • 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
    • 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 Plazza 🎉

@netlify
Copy link

netlify bot commented Oct 24, 2022

Deploy Preview for boosted ready!

Name Link
🔨 Latest commit e652aa3
🔍 Latest deploy log https://app.netlify.com/sites/boosted/deploys/635fb34e6d2db0000835776a
😎 Deploy Preview https://deploy-preview-1568--boosted.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

@julien-deramond julien-deramond added this to Triage in v5.2.1 via automation Oct 24, 2022
@julien-deramond julien-deramond moved this from Triage to In progress in v5.2.1 Oct 24, 2022
@julien-deramond julien-deramond marked this pull request as ready for review October 31, 2022 10:54
Copy link
Member

@louismaximepiton louismaximepiton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Few comments but fine for me

CHANGELOG.md Show resolved Hide resolved
CHANGELOG.md Show resolved Hide resolved
@sonarcloud
Copy link

sonarcloud bot commented Oct 31, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@julien-deramond julien-deramond merged commit 8bdb86c into main Oct 31, 2022
@julien-deramond julien-deramond deleted the main-jd-release-5.2.1 branch October 31, 2022 11:38
@julien-deramond julien-deramond moved this from In progress to Done in v5.2.1 Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

None yet

2 participants