Require peer dependency review on release PR

[antico5]

This PR introduces a workflow that checks for the presence of the "peer dependencies reviewed" label on the release PR. Since that PR is created by a workflow itself, it can't trigger other ones. For this, a step was added after the changesets/action to mark the PR as draft. Then, when an user manually marks it for ready for review, the label check workflow is ran.

The goal of this workflow is to ensure the person doing the release manually checks for peer dependency version range bumps.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 616f234

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kanej]

What is the difference between this check and stating the branch in the on section?