Problem

The composite action's "Request publish" step always creates a GitHub issue in a dedicated publish repository (defaulting to {owner}/publish). Personal repos and small orgs don't have this repo, causing the action to fail.

See: https://github.com/BYK/opencode-lore/actions/runs/22450348783

Solution

Add support for a "self" sentinel value on the existing publish_repo input. When set, the publish request issue is created in the source repository itself instead of a separate publish repo — where the default GITHUB_TOKEN already has issue write access.

Changes

• action.yml: Resolve PUBLISH_REPO=self → $GITHUB_REPOSITORY in bash before any gh CLI calls
• docs/ and README.md: Document the "self" option for publish_repo

Usage

uses: getsentry/craft/.github/workflows/release.yml@v2
with:
  version: auto
  publish_repo: self

No changes to release.yml — it already passes publish_repo through as-is.