When creating a PR that I planned on cherrypicking into beta and stable, I added the cp: beta and cp: stable labels immediately when creating the PR thinking it would trigger CP PRs to be generated when the PR landed on main. However, it appears these labels are ignored if the PR is not already merged and the CP infrastructure won't automatically create the CP PRs until the PR is merged and the labels are removed and reapplied.

To avoid this, the automated CP workflow should either be updated to check for the cp: * labels when a PR is merged or it should remove the labels if they're added before a PR is merged and leave a comment stating that the labels can only be added after the PR lands.