Lars Kappert
Lars Kappert
Thanks for all the details. Just a quick idea for now, did you try this already? Using `"type": "module"` with `-c` or `--config` like so: ``` release-it --config .release-it.mjs ```...
Inside a plugin you have access to `this.config`, so I think you should be able to do this: ```js this.config.setContext({ git: {commitMessage: 'my updated message' } }) ``` This could...
Oops, I didn't actually try it. Also tbh it didn't really sit right with me in the first place (change config of one plugin from another plugin).
Feel free to open pull request(s), I'm happy to look into them.
Sorry I'm late to the party, but is this still an issue? I've done a few updates of dependencies in the meantime.
Feel free to open a PR! I welcome PRs for sure and I'm happy to review. A draft PR is fine and I'm sure we'll sort it out.
Is this still an issue? I'm not sure where to start looking for, are you sure it's an issue in release-it?
Hopefully by now the latest versions of Node.js, release-it and updated dependencies I would expect this issue to be sorted. So I'm closing this issue, but feel free to discuss...
I don't have much experience with GitLab, but I guess the tag must be present in order to create a tag on the remote. Which needs to be pushed first?...
Looks like the [referenced issue](https://github.com/release-it/release-it/issues/1115) has a PR attached that should fix this issue. Feel free to help out over there.