Marco Ieni
Marco Ieni
yes, we just need to make sure to use the same release-plz config: https://github.com/MarcoIeni/release-plz/blob/c5eed2fb325420582b8ad7ede4ccbae74fa69fd9/crates/release_plz_core/src/changelog.rs#L225 I need to document this better
I guess you can define one group for each crate :) Having one PR for each crate, seems like a use case that could be enabled by this feature. But...
sassman is working on this https://github.com/MarcoIeni/release-plz/issues/1387#issuecomment-2065440110
> Am I correct to assume this? I don't think it's needed to refactor the functions, yes 👍
Hey @jdidion do you still work on this? No pressure of course. I'm asking because if you are no longer working on this, maybe someone else wants to pick the...
So far the PR looks great! > I'm thinking I need some higher level interface which can abstract whether the package information is coming from the registry or the git...
Hi, thanks for opening the issue! > Changing code that uses newer versions than the MSRV should also be a breaking change I heard different thoughts on this. Do you...
> Maybe it would be nice just to update the MSRV file as part of a release? Usually I've seen msrv being tested in CI. This means that people update...
Yeah, then I'm fine with this change 👍
This feature is handy if you don't want release-plz to open a PR for changes in every file. E.g. if you don't want release-plz to raise a PR for a...