ci: set token explicitly instead of using env

[mrlubos]

No description provided.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 45f7d94

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hey-api-docs	Building	Preview, Comment	Apr 14, 2026 0:21am

[pullfrog]

Reviewed — no issues found.

Task list (3/3 completed)

• Read the PR diff
• Analyze the change and check for issues
• Submit review

  ^{｜ View workflow run ｜ 𝕏}

[pullfrog]

TL;DR — Switches the GitHub release step from passing the token via the GITHUB_TOKEN environment variable to using the action's explicit token input parameter, which is the recommended way to authenticate with actions/create-release (or the underlying API call).

Key changes

• Use token input instead of GITHUB_TOKEN env var for release creation — Replaces the env.GITHUB_TOKEN block with the token parameter directly on the action step, ensuring the app token is passed explicitly rather than through the environment.

_{Summary ｜ 1 file ｜ 1 commit ｜ base: main ← ci/release-token-value}

This is a single-feature PR — the change is minimal and self-contained.

Before: The app token was set as the GITHUB_TOKEN environment variable on the release step.
After: The app token is passed directly via the token input parameter.

This aligns with the standard pattern for GitHub Actions that accept authentication tokens as explicit inputs rather than relying on environment variables.

.github/workflows/release.yml

  ^{｜ View workflow run ｜ Triggered by Pullfrog ｜ 𝕏}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 40.08%. Comparing base (fe08b45) to head (45f7d94).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3760      +/-   ##
==========================================
- Coverage   40.11%   40.08%   -0.03%     
==========================================
  Files         521      521              
  Lines       19261    19273      +12     
  Branches     5733     5727       -6     
==========================================
  Hits         7726     7726              
- Misses       9339     9345       +6     
- Partials     2196     2202       +6     

Flag	Coverage Δ
unittests	40.08% <ø> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.