From 7e3e491b1ff00fa371168915454d8e477c10cf02 Mon Sep 17 00:00:00 2001 From: Mack Date: Thu, 30 Jul 2026 00:15:36 +0800 Subject: [PATCH 1/3] chore(pkg): bump version to 0.4.0 Prepare the minor release that includes FSRS flashcard review while keeping package and lockfile version metadata aligned. --- package-lock.json | 4 ++-- package.json | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/package-lock.json b/package-lock.json index 7cf5733..336b749 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "pi-language-tutor", - "version": "0.3.0", + "version": "0.4.0", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "pi-language-tutor", - "version": "0.3.0", + "version": "0.4.0", "license": "MIT", "dependencies": { "glimpseui": "^0.8.1", diff --git a/package.json b/package.json index 0481fe7..bffaa32 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "pi-language-tutor", - "version": "0.3.0", + "version": "0.4.0", "description": "Pi extension for learning a foreign language while coding: background writing feedback (spelling, grammar, natural phrasing) on your prompts and bilingual translation of assistant responses", "type": "module", "license": "MIT", From 31121a9bcf9a16674bd2b5b3f155c6e452e86b9d Mon Sep 17 00:00:00 2001 From: Mack Date: Thu, 30 Jul 2026 00:23:35 +0800 Subject: [PATCH 2/3] docs: align release steps with version bump PRs Document the branch-protected release flow so maintainers bump version metadata through a PR, then tag the merged commit without accidentally advancing to the next version. --- AGENTS.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 2a89bb2..92252d3 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -33,13 +33,21 @@ not adjectives. ## Releases -1. Merge PRs into `main`. -2. `npm version minor|patch -m "chore(release): %s"` (bumps, commits, tags `vX.Y.Z`). -3. `git push --follow-tags` -4. `gh release create vX.Y.Z --verify-tag --generate-notes` — publishing the +1. From the latest `main`, create a branch named `chore/bump-version-X.Y.Z`. +2. Run `npm version minor|patch --no-git-tag-version`, commit only + `package.json` and `package-lock.json` as `chore(pkg): bump version to X.Y.Z`, + then open and merge the version-bump PR. +3. Update local `main` to the merged commit, then create and push its annotated + tag: `git tag -a vX.Y.Z -m "chore(release): X.Y.Z"` followed by + `git push origin vX.Y.Z`. +4. Run `gh release create vX.Y.Z --verify-tag --generate-notes` — publishing the GitHub release triggers `.github/workflows/publish.yml`, which publishes to npm via OIDC trusted publishing (no tokens). +Do not run `npm version` again after the bump PR is merged; the merged manifest +already contains the release version, and another minor/patch bump would advance +it to the next version. + The npm tarball is whitelisted by `files` in package.json; if you add runtime files outside `src/`, update it and sanity-check `npm pack --dry-run`. From d4b82fb688ae9f8c94d998c0601dabc88e606ddd Mon Sep 17 00:00:00 2001 From: Mack Date: Thu, 30 Jul 2026 00:35:28 +0800 Subject: [PATCH 3/3] docs: move release workflow update to separate PR Keep this version bump manifest-only; the release procedure update now lives in #23. --- AGENTS.md | 16 ++++------------ 1 file changed, 4 insertions(+), 12 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 92252d3..2a89bb2 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -33,21 +33,13 @@ not adjectives. ## Releases -1. From the latest `main`, create a branch named `chore/bump-version-X.Y.Z`. -2. Run `npm version minor|patch --no-git-tag-version`, commit only - `package.json` and `package-lock.json` as `chore(pkg): bump version to X.Y.Z`, - then open and merge the version-bump PR. -3. Update local `main` to the merged commit, then create and push its annotated - tag: `git tag -a vX.Y.Z -m "chore(release): X.Y.Z"` followed by - `git push origin vX.Y.Z`. -4. Run `gh release create vX.Y.Z --verify-tag --generate-notes` — publishing the +1. Merge PRs into `main`. +2. `npm version minor|patch -m "chore(release): %s"` (bumps, commits, tags `vX.Y.Z`). +3. `git push --follow-tags` +4. `gh release create vX.Y.Z --verify-tag --generate-notes` — publishing the GitHub release triggers `.github/workflows/publish.yml`, which publishes to npm via OIDC trusted publishing (no tokens). -Do not run `npm version` again after the bump PR is merged; the merged manifest -already contains the release version, and another minor/patch bump would advance -it to the next version. - The npm tarball is whitelisted by `files` in package.json; if you add runtime files outside `src/`, update it and sanity-check `npm pack --dry-run`.