Highlights ✨

Update version in package.json

Thanks to @Mattzi it is now possible to use releaser-pleaser in Javascript/Node.js projects with a package.json file.

You can enable this with the option updaters: packagejson in the GitHub Actions / GitLab CI/CD config.

All updaters, including the defaults changelog and generic can now be enabled and disabled through this field. You can find a full list in the documentation.

Features

• add updater for package.json (#213)
• highlight breaking changes in release notes (#234)

Bug Fixes

• filter out empty updaters in input (#235)
• github: duplicate release pr when process is stopped at wrong moment (#236)

Bug Fixes

• gitlab: support fast-forward merges (#210)

✨ Highlights

Reduced resource usage

releaser-pleaser now uses less resources:

• It now skips pushing changes to the release pull request if they are only a rebase.
• The configurations for GitHub Actions and GitLab CI/CD now makes sure that only a single job is running at the same time. On GitHub unnecessary/duplicate jobs are also automatically aborted.
• It handles the stop signals from the CI environment and tries to exit quickly.

Users on GitHub should add this snippet to their releaser-pleaser workflow:

concurrency:
  group: releaser-pleaser
  cancel-in-progress: true

Avoid losing manual edits to release pull request

Before, releaser-pleaser was prone to overwriting user changes to the release pull request if they were made after releaser-pleaser already started running. There is now an additional check right before submitting the changes to see if the description changed, and retry if it did.

Proper commit authorship

Before, the release commits were created by releaser-pleaser <>. This was ugly to look at. We now check for details on the API user used to talk to the forge, and use that users details instead as the commit author. The committer is still releaser-pleaser.

Features

• real user as commit author (#187)
• avoid pushing release branch only for rebasing (#114)
• colorize log output (#195)
• graceful shutdown when CI job is cancelled (#196)
• detect changed pull request description and retry process (#197)
• run one job concurrently to reduce chance of conflicts (#198)

Bug Fixes

• crash when running in repo without any tags (#190)

Bug Fixes

• invalid version for subsequent pre-releases (#174)

Features

• gitlab: make job dependencies configurable and run immediately (#101)
• github: mark pre-releases correctly (#110)

Bug Fixes

• use commits with slightly invalid messages in release notes (#105)
• create CHANGELOG.md if it does not exist (#108)

Bug Fixes

• action: container image reference used wrong syntax (#96)

Bug Fixes

• gitlab: release not created when release pr was squashed (#86)

✨ Highlights

GitLab Support

You can now use releaser-pleaser with projects hosted on GitLab.com and self-managed GitLab installations. Check out the new tutorial to get started.

Features

• add support for GitLab repositories (#49)
• add shell to container image (#59)
• gitlab: add CI/CD component (#55)
• changelog: omit version heading in forge release notes
• gitlab: support self-managed instances (#75)

Bug Fixes

• parser: continue on unparsable commit message (#48)
• cli: command name in help output (#52)
• parser: invalid handling of empty lines (#53)
• multiple extra-files are not evaluated properly (#61)

v0.4.0-beta.1

Features

• add shell to container image (#59)
• gitlab: add CI/CD component (#55)

Bug Fixes

• multiple extra-files are not evaluated properly (#61)

v0.4.0-beta.0

Features

• add support for GitLab repositories (#49)

Bug Fixes

• parser: continue on unparsable commit message (#48)
• cli: command name in help output (#52)
• parser: invalid handling of empty lines (#53)