Repair Release Please detection of merged release PRs #142

🤖 [rubykatzen/baseline]:

Problem

Release Please updates release PRs correctly, but does not create GitHub releases
after they are merged. The release job succeeds with
release_created == false, so the dependent publish job is skipped.

This happened twice:

• chore: release 0.10.0 #133 updated the repository to 0.10.0, but no v0.10.0 tag or release was
  created.
• chore: release 0.11.0 #140 updated the repository to 0.11.0, but no v0.11.0 tag or release was
  created and the gem was not published.

The repository currently configures skip-labeling: true. Release Please uses
the autorelease: pending lifecycle label together with the release branch name
to identify merged release PRs that need tagging. Without that label, merged
release PRs are not recognized.

v0.10.0 may remain intentionally skipped. Recovery should publish the current
repository version as v0.11.0.

Repair

• Remove skip-labeling: true from the Release Please action.
• Restore the Release Please lifecycle labels required for release
  detection.
• Mark merged PR chore: release 0.11.0 #140 so Release Please can recognize it as the pending
  0.11.0 release.
• Rerun Release Please and verify that it creates v0.11.0 and the GitHub
  release.
• Verify that the publish job uploads rubykatzen-baseline version 0.11.0.
• Verify that floating tags v0 and v0.11 point to v0.11.0.
• Confirm that the next generated release PR carries the expected lifecycle
  label and is recognized after merge.

Done when

Merging a Release Please PR reliably creates its version tag and GitHub release,
runs package publication, and updates floating tags without manual recovery.

🏷️ 🔧 ✅