Skip to content

Tighten release token handling #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Quantumlyy merged 4 commits into from
Apr 7, 2026
Merged

Tighten release token handling #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
14854c0
ci: add release token fallback
Quantumlyy Apr 7, 2026
aa4b440
docs: note release PR permissions
Quantumlyy Apr 7, 2026
4289e47
docs: remove release permission note
Quantumlyy Apr 7, 2026
9eb2c8c
docs: remove release section
Quantumlyy Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,5 +38,7 @@ jobs:
commit: Version packages
title: Version packages
env:
GITHUB_TOKEN: ${{ github.token }}
# Fall back to the default workflow token, but allow a PAT/App token
# because GitHub can block PR creation with `github.token` at the repo level.
GITHUB_TOKEN: ${{ secrets.RELEASE_GITHUB_TOKEN || github.token }}
NPM_CONFIG_PROVENANCE: true
12 changes: 0 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,18 +27,6 @@ Place the plugin source in your project's `.opencode/plugins/` directory (or `~/
}
```

## Releasing

For publishable changes, add a changeset with:

```sh
bun run changeset
```

Merges to `main` open or update a Changesets release pull request with the pending version and changelog updates. Merging that release pull request publishes the package to npm and creates a GitHub release.

Routine CI, config, or docs-only changes do not need a changeset unless a maintainer decides they should be released. This repo does not add PR-level changeset enforcement.

## Configuration

All configuration is via environment variables:
Expand Down
Loading