build(release): pin landmark@v0 and release with the workflow token

[moomooskycow]

Part of the fleet 0.x reset (Powder landmark-017). Landmark v0 line = pre-stable mode.

GH_RELEASE_TOKEN is expired and being retired; this workflow now releases with ${{ github.token }} instead.

Changes

• .github/workflows/landmark-release.yml: misty-step/landmark@v1 -> @v0
• .github/workflows/landmark-release.yml: github-token now uses ${{ github.token }} instead of secrets.GH_RELEASE_TOKEN

🤖 Generated with Claude Code

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[cursor]

PR Summary

Medium Risk
Release automation and GitHub auth changed; a mis-scoped default token or Landmark v0 behavior could block or mis-create releases.

Overview
Aligns the release intelligence workflow with the fleet Landmark 0.x line by pinning misty-step/landmark from v1 to v0 (pre-stable mode per landmark-017).

Replaces the retired GH_RELEASE_TOKEN secret with ${{ github.token }} for Landmark’s GitHub API calls, relying on the job’s existing contents / issues / pull-requests write permissions.

^{Reviewed by Cursor Bugbot for commit 6451a7f. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_5693dcd5-1075-4966-8e2f-6e236799472f)

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 63ef6e07-88b8-4995-814b-fa5b40d110e1

📥 Commits

Reviewing files that changed from the base of the PR and between c654f6e and 6451a7f.

📒 Files selected for processing (1)

• .github/workflows/landmark-release.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch landmark-v0-repin

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🎉 This PR is included in version 1.19.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀