Reenable automerge for new version PRs of community packages

[ringods]

Hello!

• Vote on this issue by adding a 👍 reaction
• If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

In #2705, automerge got disabled for new version PRs of community packages due to some artifacts missing from the community package.

Since then, I have been following up on the PRs created by the "new version check" workflow for community packages and hitting the merge button manually for these.

Since the introduction of the pull request template (#3366) to add a new community package, new community packages have a "complete" setup before the first version of the package gets published in our registry. The new version PRs for community packages rarely have a failing build because of the initial completeness check.

Can we enable automerge again for new version PRs having a green build?

Affected area/feature

Registry publishing for community packages.

[sean1588]

I'd be completely fine with enabling auto-merge for these PRs that are just new version releases, as we manually just push these through anyway whenever we see them. I think the only ones that should need a manual check are the initial PRs to add the package, but any version updates following should just auto-merge. I am fairly confident in this since we build all the packages anyway on a PR build now so if something was to break the build, it wouldn't be able to merge through anyway. What do you think @cnunciato?