Support package configuration in the package's directory

[epage]

Motivations

When working in larger workspaces, its much easier to have a package be an atomic unit that you can then copy, etc. This doesn't jive with having all of the config in a central file.

• Would you like to implement this feature? maybe

Solution

Support a config file in the package's directory, whether that be release-plz.toml or the Cargo.tomls package.metadata.release-plz.

Alternatives

Additional context

See #1019

[marcoieni]

This is a great idea! The package-level configuration should support the options listed here, except "name", which is inferred by the directory where release-plz.toml is placed or Cargo.toml file.
PR welcome!

[orhun]

I would like to work on this feature ✋🏼 feel free to assign it to me!

[marcoieni]

Sure thing, thanks Orhun!

[marcoieni]

You can extract package metadata with this. Also feel free to raise two PRs:

• one to support package metadata
• one to support local release-plz.toml

Or just one of the two is fine. I would avoid having one PR for both features to minimize PR length 👍

EDIT:

Requirements

• if workspace is duplicated among metadata and release-plz.toml, throw an error.
• If a package config is both present in release-plz.toml and cargo metadata, throw an error.

[orhun]

I created a draft PR at #1082 - please check.

About the requirements, how it works is it first checks the current directory for release-plz.toml/.release-plz.toml and uses them if they exist. If not, it parses the metadata from <project_dir>/Cargo.toml and uses that. Do you still want to check if they both exist and throw an error?

[marcoieni]

Do you still want to check if they both exist and throw an error?

That would be nice, yes!

[orhun]

PR is updated!

[marcoieni]

I closed #1082 for inactivity.
If anybody wants to implement this feature request, you can look at that PR as a starting point 👍