Output should be calculated and available for the tag even when skip-github-release is set to true

[SoulPancake]

When skip-github-release: true is set, release-please-action should still output the calculated tag (for example v1.2.3).

Skipping GitHub Release creation should only skip the creation step, not hide computed metadata that is useful to downstream workflow steps.

We use release-please for version/tag calculation, but create releases in later custom steps. Without a tag output, workflows must parse PR data or reconstruct the tag manually.

Please expose the computed tag output even when GitHub Release creation is skipped (including per-component/path outputs where relevant).

[non7top]

We're building a PR-preview bot: on every push to a PR, comment with exactly what merging it into master would trigger (version bump + changelog), so contributors can see the impact before merging, not after. We also add a label to PRs that would trigger a release, so they're easy to spot in the PR list.

We tried driving this off the action itself with skip-github-pull-request: true + skip-github-release: true, targeting the PR's own branch as if it were master, expecting to read prs_created/pr/version back to build the comment/label decision. Confirmed via a debug step (real feat: commit, real run) that with both skip flags set, prs_created, pr, release_created, and version all come back completely empty — not just falsy — even though the commit was genuinely releasable.

Ended up falling back to shelling out to the release-please CLI's own --dry-run and grepping its text output, which works but duplicates logic the action already computes internally, and is more fragile: it already cost us two parsing bugs on our end, and any future change to the CLI's text output format could silently break the grep again without us knowing until something misbehaves — vs. a structured output that would just change shape predictably (or be versioned).

+1 on exposing the computed values regardless of whether creation is actually skipped — would let this kind of PR-preview/labeling workflow use the action directly instead of a second CLI invocation.