[[TOC]]
This project adheres to Semantic Versioning. Before making the release, it must be decided if it is a major, minor or patch release.
If you are making a change that will require an upcoming major or minor version
increment, update the planned version for the next release in parentheses after
the Unreleased
heading in CHANGELOG.md
. Remember to also update the diff
link for this heading at the bottom of CHANGELOG.md
.
-
Create a local branch and name it e.g.
release-of-version-<version>
Example:
release-of-version-4.1.1
-
Edit
package.json
and update theversion
field. -
Run
npm install
-
Commit the changes with the commit message "update version to <version>".
-
Edit
CHANGELOG.md
Add the new release just below the
[Unreleased]
heading.At the bottom of the file, add an entry for the new version. These entries are not visible in the rendered page, but are essential for the version links to the GitLab commit comparisons to work.
Example:
+## [4.1.1] +
-[Unreleased]: https://github.com/magjac/d3-graphviz/compare/v4.1.0...HEAD +[Unreleased]: https://github.com/magjac/d3-graphviz/compare/v4.1.1...HEAD +[4.1.1]: https://github.com/magjac/d3-graphviz/compare/v4.1.0...v4.1.1 [4.1.0]: https://github.com/magjac/d3-graphviz/compare/v4.0.0...v4.1.0 [4.0.0]: https://github.com/magjac/d3-graphviz/compare/v3.2.0...v4.0.0 [3.2.0]: https://github.com/magjac/d3-graphviz/compare/v3.1.0...v3.2.0
-
Commit the changes with the commit message "add version <version> to CHANGELOG.md".
-
Push:
Example:
git push origin release-of-version-4.1.1
-
Wait until the GitHub action has run for your branch and check that it's green
-
Create a pull request
-
Merge the pull request
-
Fetch the new
master
-
Create a new tag.
Example:
git tag v4.1.1
-
Push the new tag.
Example:
git push origin refs/tags/v4.1.1
-
Use the Chose a tag dropdown to select the new tag.
-
Set the Release title to v<version>
Example:
v4.1.1
-
In the Describe this release area, type e.g.:
See the [CHANGELOG]([Title](https://github.com/magjac/d3-graphviz/blob/master/CHANGELOG.md#411--2022-04-09)) for details.
Be careful the get the mangled version correct. In this example 411
stands for 4.1.1
.
- Click Publish the release.
-
Clone the repo into clean directory
-
Run
npm install
-
Run
npm run build
-
Run
npm publish