ceos/opencode
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(http-recorder): prepare independent beta release

Browse source
This commit is contained in:
Kit Langton 2026-06-22 18:12:14 -04:00
commit 81eea42e80
17 changed files with 485 additions and 85 deletions
Download patch file Download diff file Expand all files Collapse all files

33
packages/http-recorder/RELEASE.md Normal file
View file

@ -0,0 +1,33 @@
# Release
`@opencode-ai/http-recorder` is versioned independently from OpenCode and published under the npm `beta` tag.
## Prepare A Release
1. Add a Changeset for every user-facing package change.
2. Run `bunx changeset status` and confirm that only `@opencode-ai/http-recorder` will be bumped.
3. Merge the package changes into `dev`.
4. From a branch based on the latest `dev`, run `bun run version:http-recorder`.
5. Review the generated version and `packages/http-recorder/CHANGELOG.md`, then open and merge the release PR.
The first minor Changeset advances the unpublished `0.0.0` package to `0.1.0`. OpenCode's repository-wide release script deliberately excludes this package from its version synchronization.
## Verify And Publish
Before merging the release PR, run these commands from `packages/http-recorder`:
```sh
bun run test
bun typecheck
bun run verify:package
```
After the release PR reaches `dev`, manually dispatch the `http-recorder release` workflow from the `dev` branch. The workflow repeats the focused tests, builds and verifies the exact tarball in a clean npm consumer, and publishes it with provenance under the `beta` tag.
The bootstrap release requires an npm automation token in the repository's `NPM_TOKEN` secret. After the package exists, configure npm trusted publishing for `.github/workflows/http-recorder-release.yml` and the `npm` GitHub environment, then remove the token so later releases use GitHub OIDC.
Verify the result:
```sh
npm view @opencode-ai/http-recorder version dist-tags --json
```