Skip to content

Releases: apricote/releaser-pleaser

v0.5.0

15 Nov 17:55
b617232
Compare
Choose a tag to compare

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)

v0.4.2

08 Nov 12:29
05be368
Compare
Choose a tag to compare

Bug Fixes

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

v0.4.1

17 Oct 17:25
1883466
Compare
Choose a tag to compare

Bug Fixes

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

v0.4.0

25 Sep 11:07
4cc45ea
Compare
Choose a tag to compare

✨ 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

15 Sep 19:00
dc1903c
Compare
Choose a tag to compare

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

15 Sep 15:19
84d4dd9
Compare
Choose a tag to compare

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)

v0.3.0

06 Sep 21:47
0a199e6
Compare
Choose a tag to compare

v0.3.0

✨ Highlights

Cleaner pre-release Release Notes

From now on if you create multiple pre-releases in a row, the release notes will only include changes since the last pre-release. Once you decide to create a stable release, the release notes will be in comparison to the last stable release.

Edit pull request after merging.

You can now edit the message for a pull request after merging by adding a ```rp-commits code block into the pull request body. Learn more in the Release Notes Guide.

Features

  • less repetitive entries for prerelease changelogs #37
  • format markdown in changelog entry (#41)
  • edit commit message after merging through PR (#43)
  • cli: show release PR url in log messages (#44)

v0.2.0

25 Aug 21:02
1f39df0
Compare
Choose a tag to compare

v0.2.0

Features

  • update version references in any files (#14)
  • cli: add --version flag (#29)

Bug Fixes

  • ci: building release image fails (#21)
  • ci: ko pipeline permissions (#23)
  • action: invalid quoting for extra-files arg (#25)

v0.2.0-beta.2

24 Aug 13:27
0f8d3cc
Compare
Choose a tag to compare

v0.2.0-beta.2

Features

  • update version references in any files (#14)

Bug Fixes

  • ci: building release image fails (#21)
  • ci: ko pipeline permissions (#23)

v0.2.0-beta.1

24 Aug 13:15
e96e510
Compare
Choose a tag to compare

v0.2.0-beta.1

Features

  • update version references in any files (#14)

Bug Fixes

  • ci: building release image fails (#21)