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.
Documentation for the release process of Leaflet.
Please note that you will need to have a git remote called
origin
that points to Leaflet's GitHub repo, since the publish script assumes itprepare-X.Y.Z
)package.lock.json
oryarn.lock
locally, since they can potentially make you build with the wrong package versions/docs/_posts
and commit to the release branchpackage.json
and commit tomaster
npm run release
npm run docs
dist/reference-X.Y.Z.html
todocs/reference-X.Y.Z.html
docs/reference.html
to redirect to the new version and commit the change to the release branchgit checkout vX.Y.Z
)npm run integrity
or simplynode ./build/integrity.js
if you're not on Debianintegrity_hash_css
,integrity_hash_source
andintegrity_hash_uglified
indocs/_config.yml
; commit changes to the release branchdocs/download.html
, and commit to the release branchdocs/reference-versions.html
, and commit to the release branchlatest_leaflet_version
indocs/_config.yml
and commit to the release branchdocs/index.html
and commit to the release branchmaster