Skip to content

pr-status: expose the release plan as a structured output #690

Open

Description

@materwelonDhruv

pr-status already computes the full release plan (via @changesets/get-release-plan) to build its comment, then only exposes comment-body. Could it also surface that same data as structured outputs?

These would be suuuper useful:

  • max-bump: the highest of major/minor/patch across the released packages, or none
  • releases: JSON array of { name, type, oldVersion, newVersion } per package

The current code for this action already carries all of this (per-package type plus old and new versions), so nothing new needs computing.

I currently label a PR patch/minor/major from the bump by manually parsing the files in the .changesets folder. The code for that would become much simpler if I could get these outputs directly. And this action already handles the pull_request_target fork-safety, so I wouldn't have to worry about that.

I already have a draft locally for this, but I wanted to check if this is something you'd be open to before I submit it. If so, I can clean it up and submit a PR. Pls lmk!

Activity

  1. Andarist commented on Jul 2, 2026

    @Andarist
    Member

    Sounds reasonable. We should probably wait until we land this #689 to decide how to expose this information here (this would ensure we'd expose those kind of outsputs in a consistent way)

  2. materwelonDhruv commented on Jul 2, 2026

    @materwelonDhruv
    Author

    Oki. I wonder if there's a way to watch a PR. Either way, will get back to this once 689 is resolved 👍🏻

  3. beeequeue commented on Jul 2, 2026

    @beeequeue
    Member

    there should be a Subscribe button on the right. 🙂

  4. materwelonDhruv commented on Jul 2, 2026

    @materwelonDhruv
    Author

    omg 😭 my brain just filtered that out given how many times I've looked at it and NOT used it.

  5. materwelonDhruv commented on Jul 24, 2026

    @materwelonDhruv
    Author

    #689 just got resolved 😄 are you okay with me opening a PR for this @Andarist ?

  6. Andarist commented on Jul 24, 2026

    @Andarist
    Member

    sure, go ahead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions