feat: Add package.json updater #213
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👋 @apricote any update on this topic ? |
|
Hey @Mattzi, thank you for the contribution! I have changed some things around the configuration, that I will push and merge in a follow up Pull Request. Particularly I would like to make this more generic to allow other updaters in the future without having to add a new flag for each one. Instead there will be |
apricote
approved these changes
Aug 23, 2025
This was referenced Aug 23, 2025
apricote
pushed a commit
to hetznercloud/fleeting-plugin-hetzner
that referenced
this pull request
Aug 27, 2025
…etznercloud/fleeting-plugin-hetzner!272) This MR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [apricote/releaser-pleaser](https://gitlab.com/apricote/releaser-pleaser) | repository | minor | `v0.6.1` -> `v0.7.0` | --- ### Release Notes <details> <summary>apricote/releaser-pleaser (apricote/releaser-pleaser)</summary> ### [`v0.7.0`](https://gitlab.com/apricote/releaser-pleaser/blob/HEAD/CHANGELOG.md#v070) [Compare Source](https://gitlab.com/apricote/releaser-pleaser/compare/v0.6.1...v0.7.0) ##### Highlights ✨ ##### Update version in `package.json` Thanks to [@​Mattzi](https://github.com/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](https://apricote.github.io/releaser-pleaser/reference/updaters.html). ##### Features - add updater for package.json ([#​213](apricote/releaser-pleaser#213)) - highlight breaking changes in release notes ([#​234](apricote/releaser-pleaser#234)) ##### Bug Fixes - filter out empty updaters in input ([#​235](apricote/releaser-pleaser#235)) - **github**: duplicate release pr when process is stopped at wrong moment ([#​236](apricote/releaser-pleaser#236)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS44Mi4xMCIsInVwZGF0ZWRJblZlciI6IjQxLjgyLjEwIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Thank you for creating this, I've really liked it so far.
I've implemented a solution for issue #118 , which addresses a problem I also faced.
I'm open to any feedback regarding functionality or code style improvements.
@apricote