`linear-release-action`: add description/body input to enrich release notes

[lorenzo-attuned]

Use case

We use linear/linear-release-action@v0 to create Linear releases on every prod deploy. We also create a GitHub Release in the same workflow with detailed release notes (changelog, Sentry source maps, deploy metadata).

We'd like to link the two together — specifically, include a link to the GitHub Release page in the Linear release so team members viewing the Linear pipeline can quickly jump to the full changelog.

Why this matters

Not every commit in our repo references a Linear issue. CI/CD fixes, infra changes, and refactors often don't have associated tickets. When the action scans commits and finds no matching issue identifiers, it either skips release creation entirely ({release: null}) or creates a release with no linked issues — making the auto-generated notes unhelpful.

A GitHub Release, on the other hand, always has the full commit diff and changelog. Being able to link to it from the Linear release would give the team a reliable way to see what actually shipped, regardless of whether commits had Linear issue references.

Current limitation

The action only accepts name, version, and stage as metadata inputs. There's no way to attach a description, body, or external links to the created release.

Notably, the Linear app UI already supports adding external link attachments to releases manually — so the data model appears to support this, it's just not exposed via the CLI or action inputs.

Proposed solution

Add an optional description (or body) input that gets passed through to the Linear release:

- uses: linear/linear-release-action@v0
  with:
    access_key: ${{ secrets.LINEAR_ACCESS_KEY }}
    name: v2026.05.11.8
    version: v2026.05.11.8
    description: |
      [GitHub Release](https://github.com/org/repo/releases/tag/v2026.05.11.8)

Alternatively (or additionally), a links input to attach external URLs:

- uses: linear/linear-release-action@v0
  with:
    access_key: ${{ secrets.LINEAR_ACCESS_KEY }}
    name: v2026.05.11.8
    version: v2026.05.11.8
    links: |
      https://github.com/org/repo/releases/tag/v2026.05.11.8

This would allow teams to cross-link between their GitHub releases and Linear pipeline releases, which is especially useful when releases have no matching issue-tagged commits but a GitHub release still exists with the full diff.

Alternatives considered

• Using the Linear GraphQL API in a post-step to update the release — but the Release type doesn't appear to have an updatable description field via the API
• Linking from Slack notifications (we're doing this now, but it's one-directional — a Linear → GH link within Linear itself would be more discoverable for the team)

Originally posted in linear/linear#1138 (comment)