feat: add additional-paths property to manifest releaser

[jack-lewin]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1921 🦕

---

This PR adds an additional-paths property to the manifest releaser.

Additional paths are useful for monorepos where a package might depend files from other directories.

For example, if we want to trigger a release in apps/my-app-2 when commits are found in libs/my-lib:

apps/
    my-app-1
    my-app-2
libs/
    my-lib

{
  "packages": {
    "apps/my-app-1": {},
    "apps/my-app-2": {
      "additional-paths": ["libs/my-lib"] // additional-paths would be a new config option
    }
  }
}

Best reviewed commit-by-commit.

[jack-lewin]

Hi @chingor13, sorry for the nudge - are you still maintaining this project?
If not, is there anyone else I should reach out to?

[chingor13]

Thanks for this and sorry for the delay in reviewing.

This mostly looks fine although we should explicitly define what the expected logic is if an additional path coincides with a different component's path or additional paths. Currently, we sort by the components' path length with the longest first as a way to prefer the deepest path in the case of overlapping paths. With this new logic, we are still sorting based on the main path, and preferring its additional paths over any other ones.

Instead, we may need to invert the mapping and have the keys be all the "paths" (main & additional) and the value is the main component path to associate to.

[sylwit]

Hi @jack-lewin will you have time to update your PR or do you need help ? Thank you for this PR

[roivanov]

sync with the latest main: jack-lewin#1