pi-pr-review 1.9.0 → 1.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -36,6 +36,36 @@ jobs:
|
|
|
36
36
|
manifest-file: .release-please-manifest.json
|
|
37
37
|
token: ${{ steps.app-token.outputs.token }}
|
|
38
38
|
|
|
39
|
+
- name: Enable squash auto-merge for release PRs
|
|
40
|
+
if: ${{ steps.release.outputs.prs_created == 'true' }}
|
|
41
|
+
env:
|
|
42
|
+
GH_TOKEN: ${{ steps.app-token.outputs.token }}
|
|
43
|
+
RELEASE_PRS: ${{ steps.release.outputs.prs }}
|
|
44
|
+
run: |
|
|
45
|
+
jq -r '.[].number' <<< "$RELEASE_PRS" | while read -r number; do
|
|
46
|
+
merge_method="$(gh pr view "$number" --repo "$GITHUB_REPOSITORY" --json autoMergeRequest --jq '.autoMergeRequest.mergeMethod // "NONE"')"
|
|
47
|
+
echo "Release PR #$number auto-merge method: $merge_method"
|
|
48
|
+
|
|
49
|
+
case "$merge_method" in
|
|
50
|
+
SQUASH)
|
|
51
|
+
echo "Squash auto-merge is already enabled for release PR #$number"
|
|
52
|
+
continue
|
|
53
|
+
;;
|
|
54
|
+
MERGE|REBASE)
|
|
55
|
+
echo "Replacing $merge_method auto-merge for release PR #$number"
|
|
56
|
+
gh pr merge "$number" --repo "$GITHUB_REPOSITORY" --disable-auto
|
|
57
|
+
;;
|
|
58
|
+
NONE)
|
|
59
|
+
;;
|
|
60
|
+
*)
|
|
61
|
+
echo "Unexpected auto-merge method for release PR #$number: $merge_method" >&2
|
|
62
|
+
exit 1
|
|
63
|
+
;;
|
|
64
|
+
esac
|
|
65
|
+
|
|
66
|
+
gh pr merge "$number" --repo "$GITHUB_REPOSITORY" --auto --squash
|
|
67
|
+
done
|
|
68
|
+
|
|
39
69
|
publish:
|
|
40
70
|
name: Test and publish to npm
|
|
41
71
|
needs: release
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [1.10.0](https://github.com/10ego/pi-pr-review/compare/v1.9.0...v1.10.0) (2026-07-14)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Features
|
|
7
|
+
|
|
8
|
+
* **release:** auto-merge release pull requests ([#21](https://github.com/10ego/pi-pr-review/issues/21)) ([56ea9a9](https://github.com/10ego/pi-pr-review/commit/56ea9a9585069193181c78700223cb659af72750))
|
|
9
|
+
|
|
3
10
|
## [1.9.0](https://github.com/10ego/pi-pr-review/compare/v1.8.0...v1.9.0) (2026-07-14)
|
|
4
11
|
|
|
5
12
|
|
package/RELEASING.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Releasing
|
|
2
2
|
|
|
3
|
-
[Release Please](https://github.com/googleapis/release-please) watches conventional commits merged into `main`. It opens or updates a release PR containing the calculated version change, `CHANGELOG.md`, and release manifest. Its root Node strategy is the sole version writer: the generated PR keeps `package.json` and `.release-please-manifest.json` in sync. The generated PR title—and therefore its squash commit—uses `release(main): release <version>`.
|
|
3
|
+
[Release Please](https://github.com/googleapis/release-please) watches conventional commits merged into `main`. It opens or updates a release PR containing the calculated version change, `CHANGELOG.md`, and release manifest, then enables squash auto-merge for that PR. Required checks must pass before GitHub merges it. Its root Node strategy is the sole version writer: the generated PR keeps `package.json` and `.release-please-manifest.json` in sync. The generated PR title—and therefore its squash commit—uses `release(main): release <version>`. The merge creates a GitHub release and, after the test suite passes, publishes `pi-pr-review` to npm with signed provenance.
|
|
4
4
|
|
|
5
5
|
Pull-request CI verifies both root version fields remain equal. The publish job repeats that read-only check against the version emitted by Release Please, so an inconsistent release commit cannot publish; no feature PR should manually set a release version.
|
|
6
6
|
|
|
@@ -17,12 +17,13 @@ All changes to `main` must go through a pull request and use squash merging. The
|
|
|
17
17
|
## One-time setup
|
|
18
18
|
|
|
19
19
|
1. Install the private [`nerv-ops`](https://github.com/settings/apps/nerv-ops) GitHub App on this repository with **Contents: read and write** and **Pull requests: read and write** permissions.
|
|
20
|
-
2.
|
|
21
|
-
3.
|
|
20
|
+
2. Under the repository's **Settings → General → Pull Requests**, enable **Allow auto-merge** and keep squash merging enabled.
|
|
21
|
+
3. Add the App ID as the repository Actions variable `NERV_OPS_APP_ID`, and add a generated PEM private key as the repository Actions secret `NERV_OPS_PRIVATE_KEY`.
|
|
22
|
+
4. In the npm settings for [`pi-pr-review`](https://www.npmjs.com/package/pi-pr-review), add a GitHub Actions trusted publisher with:
|
|
22
23
|
- organization/user: `10ego`
|
|
23
24
|
- repository: `pi-pr-review`
|
|
24
25
|
- workflow filename: `release-please.yml`
|
|
25
26
|
- environment: leave blank
|
|
26
|
-
|
|
27
|
+
5. Use conventional titles for squash-merged PRs.
|
|
27
28
|
|
|
28
29
|
No npm token is stored in GitHub. The workflow exchanges the App credentials for a short-lived repository installation token and uses npm trusted publishing through GitHub OIDC.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-pr-review",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.10.0",
|
|
4
4
|
"description": "Parallel AI code review for GitHub pull requests in the Pi coding agent, with model-agnostic tiered subagents, structured findings, optional verification, and safe COMMENT-only publishing.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|