Multiple versions of the same buildpack in the same repository lead to unexpected behaviour

[matsluni]

In one of my repos, where I use this action I was surprised when I noticed that for a buildpack (in this case java-buildpack) not every manifest on my monorepo was updated via this action. I would have expected that all manifests are considered in the PR, but they were not.

I was investigating my repo and the source of this action and found the following line seems to be the culprit. In my case the versions in my manifests are different, and the version is considered in the grouping. So it generates multiple groups for the buildpack. In a later step the second group is ignored as a PR with the buildpackname + new_version already exists.

In my opinion a single PR should be created with all (currently different) versions of a buildpack version in the manifest files.

[matsluni]

Or a second option could be, that in the name of the PR the currentVersion is included. That way there are no name collisions for multiple versions of a buildpack.

[efasel]

Or a second option could be, that in the name of the PR the currentVersion is included. That way there are no name collisions for multiple versions of a buildpack.

I think this is a better approach. Lets keep these PRs as small as possible.