Skip to content

chore(release): publish 0.3.1 #11

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
patlux merged 2 commits into from
May 28, 2026
Merged

chore(release): publish 0.3.1 #11

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
56b212a
chore(release): publish 0.3.1
patlux May 28, 2026
c55d73d
docs(release): document branch-protected PR workflow
patlux May 28, 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
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# Changelog

## 0.3.1 - 2026-05-29

- Bump CLI version header to `0.29.0` for Command Code API parity.
- Harden PR security pipeline CI configuration.

## 0.3.0 - 2026-05-28

- Add OMP (Oh My Pi) provider compatibility: support `~/.omp/agent/auth.json` auth path, handle OMP's env-var-name-as-apiKey quirk, convert OMP system prompt arrays to text.
Expand Down
32 changes: 23 additions & 9 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,8 @@ Recommended flow:
- publish prereleases with the `next` dist-tag
- smoke-test the npm package directly in pi
- publish stable releases with the `latest` dist-tag
- commit and tag the stable release
- commit the release on a branch, open a PR, and merge after CI passes
- tag the stable release on `main` after merge
- comment on the related PR or issue after shipping

## Prerelease flow
Expand Down Expand Up @@ -144,12 +145,32 @@ npm pack --dry-run
git diff --check
```

Commit and tag:
Commit on a release branch and open a PR:

```sh
git checkout -b release/0.1.1
git add .
git commit -m "Release 0.1.1"
git push origin release/0.1.1
gh pr create --title "chore(release): publish 0.1.1" --base main
```

`main` is branch-protected. The release must go through a PR with passing CI.

Once CI passes, approve and merge:

```sh
gh pr review <number> --approve
gh pr merge <number> --squash --delete-branch
```

After merge, pull `main` and tag locally:

```sh
git checkout main
git pull origin main
git tag -a v0.1.1 -m "Release 0.1.1"
git push origin v0.1.1
```

Publish stable:
Expand All @@ -172,13 +193,6 @@ Expected:
- `latest` points to the stable version
- the stable version exists on npm

Push commit and tag:

```sh
git push origin main
git push origin v0.1.1
```

## GitHub follow-up

Comment on the related PR and issue after publishing and pushing:
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": "pi-commandcode-provider",
"version": "0.3.0",
"version": "0.3.1",
"description": "pi custom provider for Command Code API (commandcode.ai)",
"type": "module",
"keywords": [
Expand Down
Loading