-
Notifications
You must be signed in to change notification settings - Fork 54
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
🚀 v5.2.1 #1568
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for boosted ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
louismaximepiton
approved these changes
Oct 31, 2022
There was a problem hiding this 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
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specific to this version
gh-pages
modifications have been done before merging this PR:gh-pages
check the diff with twbs/bootstrap@1510239Generic
npm run release-version $current_version $next_version
to bump version numberManually changeversion_short
inpackage.json
Add docs version tosite/data/docs-versions.yml
Manually changedocs_version
inconfig.yml
and other references to the previous versionUpdate redirects in docs frontmatter (site/content/docs/_index.html
?)Movesite/content/docs/5.x
tosite/content/docs/5.x+1
Incrementsite/static/docs/{version}
versionIncrement version innuget/boosted.nuspec
Ensure Algolia indexes new release content (probably requires a PR)(Major version) Manually update the version innuget/boosted.nuspec
andnuget/boosted.sass.nuspec
CHANGELOG.md
, and maybesite/content/docs/<version>/migration.md
package-lock.json
andpackage.json
content, only "boosted" should have its version changed!site/content/docs/5.1/**/*.md
should not always be modified.scss
main files (reboot, grid, utilities and main file) as well as inNOTICE.txt
.npm run release
to compile dist, update SRI hashes in doc and package the releaseconventional-changelog-cli
globallyconventional-changelog -p angular -i CHANGELOG.md -s
dist
with achore(release)
commit messagev4-dev
ormain
)npm pack
.npmrc
file--tag
, eg for v5-alpha1npm publish boosted-5.0.0-alpha1.tgz --tag next
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)npm publish
gh-pages
:../_site
to thegh-pages
branchindex.html
used as redirections to be redirecting to the new releasedist
URLs in examples' HTML has changed