Skip to content

0.3.0 #4

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
P-Theo merged 2 commits into from
Sep 9, 2026
Merged

0.3.0 #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
532d0c3
docs: gate version bumps behind release PRs and clear the prerelease …
P-Theo Sep 9, 2026
e4a34a7
0.3.0
P-Theo Sep 9, 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
17 changes: 15 additions & 2 deletions docs/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ The host reuses the newest generation without contacting the registry, so the st

## 4. Publish a prerelease

Use a version such as `0.1.0-rc.1`.
Use a version such as `0.1.0-rc.1`, bumped and merged through a release pull request as in step 6 — before step 1, so the tarball under test is the artifact that ships.

```sh
npm publish --tag next
Expand All @@ -50,6 +50,12 @@ Always pass a tag. An untagged publish becomes `latest`, prerelease version or n

## 5. Install from the registry

Delete the `@next` cache directory first: `plugin add` reuses the newest cached generation without contacting the registry, so a prerelease left over from an earlier verification would be installed instead — and routed by its old exports map.

```sh
rm -rf ~/.cache/opencode/npm/opencode2-tps@next
```

Add the prerelease with the CLI's plugin command, which installs it into the host cache and adds the entry to `cli.json` (remove any `latest` entry first — the last entry wins):

```sh
Expand All @@ -62,9 +68,16 @@ This is the only step that exercises registry resolution, the plugin-add routing

`npm version` refuses a dirty tree, so commit the work first. It writes the version, commits it, and tags it `v<version>` to match the existing tags.

`main` only accepts commits through a pull request, so the bump travels on a release branch. Merge it with a merge commit — a rebase or squash merge rewrites the commit and leaves the tag pointing outside `main`'s history:

```sh
git checkout -b release/<version>
npm version patch
git push --follow-tags
git push -u origin release/<version>
gh pr create --base main --head release/<version> --title <version> --body "..."
gh pr merge release/<version> --merge --delete-branch --auto
git checkout main && git pull
git push origin v<version>
npm publish
```

Expand Down
4 changes: 2 additions & 2 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "opencode2-tps",
"version": "0.3.0-rc.1",
"version": "0.3.0",
"description": "Live token-throughput indicator for the OpenCode 2 TUI prompt composer",
"license": "MIT",
"author": "P-Theo",
Expand Down