Display released version that includes pull request in the PR right column

[tbertels]

🏷️ Discussion Type

Product Feedback

Body

Right now, issues linked to a PR display the version that includes the PR linked to that issue:

But PRs on the other end don't include that information, so it's harder to know which version includes them:
You have to scroll down in the PR discussion until the "merged commit 1f7a212 into mpc-qt:master"

And click on the commit hash "1f7a212".

Then you'll see something like "master(mpc-qt/mpc-qt#636) v26.07 ... v26.01-master"
at the bottom of the merge commit description:

Where "v26.01-master" is the first version that includes the commit.
This is far from straightforward for users.
Note that it says "v26.01-master" (a tag on master) instead of "v26.01" (the tag of an actual release).

Instead, PRs should have a field on the right column that would show directly that information ("v26.01", not "v26.01-master").

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Rohith-Itagi7]

I agree this would be a useful improvement. The release/tag that first contains a merged PR can currently require going through the merge commit and its associated tags, which adds unnecessary steps.

A “Included in release” field in the PR sidebar could make this much easier to discover, especially for repositories that publish releases frequently.

It would also be useful if GitHub linked directly to the first stable release containing the PR, rather than requiring users to inspect commits manually.