[rqbazan]

Summary

Text that the repo contradicted, fixed against the code:

README.md, docs/contributing.md   # pin to a SHA (the repo has no tags); preview-comment.yml runs the actions at @main;
                                  # vland-bot links the GitHub App (bot.variable.land answers 404 at its root)
actions/*preview-release/README.md
  nextVersion                     # 1.2.3 → 1.2.4-git-abc1234.0, as `pnpm version prerelease` makes it
  pnpm commands                   # the flags the code passes: --no-git-checks, --access public
  token-only                      # any .npmrc in the directory selects it, whatever it holds
  monorepo dependents             # unpublished workspace dependencies go with the changed packages; dependents don't
  packages output                 # an entry is one item of the POSTed packages array, not the payload
docs/development.md               # the ncc build, npm's min-release-age, grouped Dependabot security updates
actions/*/package.json            # descriptions in the brand voice (private, no changeset)

Evidence

• Before: git ls-remote --tags https://github.com/withvariablelab/gh-actions → empty, and the README said "pin to a tag".
  After: the README says to pin to a SHA.
• Before: <current>-git-<short-sha>.
  After: pnpm version prerelease --preid git-abc1234 on 1.2.3 gives 1.2.4-git-abc1234.0, the version the README now shows.
• mise run check passes. A second agent ran mise run test and mise run check-dist on a copy of the branch, and checked every hunk against src/.

Merge Danger

Door: two-way

Blast Radius: docs

No src/ or dist/ change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01TzjvWWSt2KQNsVgAtswGTL

[changeset-bot]

⚠️ No Changeset found

Latest commit: ee68b11

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.

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