All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
--versionflag (shorthand:-v) has been added to show the current version of@firefoxic/release-it.
5.0.0 — 2026–05–10
- Support for
npmhas been removed. Onlypnpm@11+is now supported. node.jsnow requires version22.22.0or later.
4.1.0 — 2026–02–03
@firefoxic/release-itwill now automatically updatenpmif its version is older than11.5.1, which is the minimum version required for trusted publishing. You can now remove thenpmupdate command from your GitHub Action.
4.0.1 — 2026–01–24
- The package no longer requires
pnpm. Butpnpmis highly recommended 😉
4.0.0 — 2025–12–08
- The package now uses trusted publishing instead of NPM tokens. You should remove the line with
NPM_TOKENfrom your release pipeline (and also remove theNPM_TOKENfrom secrets of your repository) and add a line withregistry-url: 'https://registry.npmjs.org'(see the changes to therelease.yamlfile as an example).
3.0.0 — 2025–09–24
- The project has been renamed to
@firefoxic/release-it. - The launch command for local installation has been renamed to
release-it. - The tool now not only updates the changelog, but also performs all other steps before and after that are necessary to publish a new version of the package. This means that you need to remove the commands and logic for raising the version and publishing it from the pipeline and scripts.
- Pre-release versions are now possible, and their names are determined based on the branch name.
- Before updating the changelog, the package version is now raised according to the version type (still selected based on the changelog content) and possible pre-release status.
- The package with the new version is now built and published to npm with the appropriate authentication —
NPM_TOKENfor CI orOTPfor local execution. - A release of the published version is now automatically created on GitHub.
2.0.2 — 2025–09–24
- URLs for links are now generated correctly.
2.0.1 — 2025–09–23
- The description in the README.md file has now been corrected.
2.0.0 — 2025–09–23
- The
update-changelogcommand should now be called not in theversionscript of the package.json file, but immediately after thepnpm version <release_type>command.
- The project has been rewritten in
bashand now does not depend on node.js or npm packages.
1.0.0 — 2024–10–30
- The minimum required
node.jsversion has been increased to20.12.0, except for version21.
0.2.1 — 2024–09–25
- The space before the dash in the version heading is now non-breaking. This hardly affects anything, but for consistency of typography it should be like this everywhere.
0.2.0 — 2024–07–30
- The
update-changelogutility now automatically stagesCHANGELOG.mdin git. You can remove&& git add CHANGELOG.mdfrom yourversionhook and leave onlyupdate-changelogin it.
0.1.0 — 2024–05–09
- The basic functionality of the
update-changelogCLI utility.