Repository navigation
chore(deps): bump the actions group across 1 directory with 7 updates - #576
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
added
security
![petry-projects-dependabot-automrg[bot]](https://avatars.githubusercontent.com/u/258516906?s=60&v=4){kind=small}
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-f3a151d1ad
branch
from
June 11, 2026 22:50
20bd72f to
5da0149
Compare
dependabot
Bot
dismissed
petry-projects-dependabot-automrg[bot]’s stale review
via
June 12, 2026 01:55
75ba2f6
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-f3a151d1ad
branch
from
June 12, 2026 01:55
5da0149 to
75ba2f6
Compare
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-f3a151d1ad
branch
from
June 12, 2026 02:19
75ba2f6 to
d25a75b
Compare
Bumps the actions group with 7 updates in the / directory: | Package | From | To | | --- | --- | --- | | [actions/checkout](https://github.com/actions/checkout) | `6.0.2` | `6.0.3` | | [petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml](https://github.com/petry-projects/.github-private) | `db60a41eb00b127f201c7294c529c7c599324e4e` | `0ef7b6150516c4fa447700b4902e8ed406bcfb99` | | [petry-projects/.github/.github/workflows/dependabot-automerge-reusable.yml](https://github.com/petry-projects/.github) | `1` | `2` | | [petry-projects/.github/.github/workflows/dependency-audit-reusable.yml](https://github.com/petry-projects/.github) | `1` | `2` | | [petry-projects/.github/.github/workflows/feature-ideation-reusable.yml](https://github.com/petry-projects/.github) | `1` | `2` | | [anthropics/claude-code-action](https://github.com/anthropics/claude-code-action) | `1.0.133` | `1.0.148` | | [SonarSource/sonarqube-scan-action](https://github.com/sonarsource/sonarqube-scan-action) | `8.1.0` | `8.2.0` | Updates `actions/checkout` from 6.0.2 to 6.0.3 - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6.0.2...df4cb1c) Updates `petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml` from db60a41 to 0ef7b61 - [Commits](db60a41...0ef7b61) Updates `petry-projects/.github/.github/workflows/dependabot-automerge-reusable.yml` from 1 to 2 - [Commits](petry-projects/.github@v1...v2) Updates `petry-projects/.github/.github/workflows/dependency-audit-reusable.yml` from 1 to 2 - [Commits](petry-projects/.github@v1...v2) Updates `petry-projects/.github/.github/workflows/feature-ideation-reusable.yml` from 1 to 2 - [Commits](petry-projects/.github@d3d768d...376a4fc) Updates `anthropics/claude-code-action` from 1.0.133 to 1.0.148 - [Release notes](https://github.com/anthropics/claude-code-action/releases) - [Commits](anthropics/claude-code-action@787c5a0...d5726de) Updates `SonarSource/sonarqube-scan-action` from 8.1.0 to 8.2.0 - [Release notes](https://github.com/sonarsource/sonarqube-scan-action/releases) - [Commits](SonarSource/sonarqube-scan-action@7006c44...7138816) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: anthropics/claude-code-action dependency-version: 1.0.144 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: actions - dependency-name: petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.yml dependency-version: 0ef7b61 dependency-type: direct:production dependency-group: actions - dependency-name: petry-projects/.github/.github/workflows/dependabot-automerge-reusable.yml dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: petry-projects/.github/.github/workflows/dependency-audit-reusable.yml dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: petry-projects/.github/.github/workflows/feature-ideation-reusable.yml dependency-version: '2' dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions - dependency-name: SonarSource/sonarqube-scan-action dependency-version: 8.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
dismissed
petry-projects-dependabot-automrg[bot]’s stale review
via
June 13, 2026 12:55
b3bce2e
dependabot
Bot
force-pushed
the
dependabot/github_actions/actions-f3a151d1ad
branch
from
June 13, 2026 12:55
d25a75b to
b3bce2e
Compare
Contributor
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
auto-merge was automatically disabled
June 13, 2026 13:04
Pull request was closed
don-petry
added a commit
that referenced
this pull request
Jul 3, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 2, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 3, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 3, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 3, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 7, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 8, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 8, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 8, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 8, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
don-petry
added a commit
that referenced
this pull request
Aug 18, 2026
…source (#575) (#1013) * chore(rulesets): repoint apply-rulesets + bootstrap to fleet source in .github (#575) The org-wide fleet rulesets (code-quality, pr-quality) now live in petry-projects/.github (standards/rulesets/, relocated there in the companion PR). Repoint the codified applier and the bootstrap orchestrator to source them from there, and remove the local copies. release-channel-tags stays repo-local. apply-rulesets.sh: - Default is now "fleet mode": when RULESETS_DIR is unset, materialize the fleet rulesets from STANDARDS_REPO (default petry-projects/.github) — via a local FLEET_RULESETS_DIR checkout when provided, else a gh contents-API fetch into a temp dir (mirrors seed-repo-template.sh's _fetch_standard model). - The repo-local release-channel-tags is applied by pointing RULESETS_DIR at this repo's own .github/rulesets (unchanged mechanism). - Remove the now-dead SCRIPT_DIR-based local default. bootstrap-new-repo.sh: - step_rulesets now applies exactly the two fleet rulesets to a new repo (fleet mode). release-channel-tags is NO LONGER applied to bootstrapped repos — it protects .github-private's own pr-review/** + dev-lead/** release tags only, so it is repo-local by the #575/#576 boundary. (Previously all 3 were applied.) Remove .github/rulesets/{code-quality,pr-quality}.json (moved to .github). Tests: - test_apply_rulesets.bats: pass RULESETS_DIR explicitly for release-channel-tags; add fleet-mode coverage (2 rulesets applied, never release-channel-tags; dry-run no-writes; missing FLEET_RULESETS_DIR errors). - test_bootstrap_new_repo.bats: provision a fleet fixture in setup so the real apply-rulesets resolves offline; drop the pr-quality/code-quality JSON *shape* assertions (that content is now owned + validated in .github); assert bootstrap applies exactly 2 fleet rulesets and not release-channel-tags. - new-repo-validation.md: 3 -> 2 ruleset(s); source-of-truth now petry-projects/.github. Migration safety (AC): relocated JSONs are byte-identical to the pre-move copies; a live --dry-run against petry-projects/.github-private resolves them and UPDATES the existing rulesets in place (PUT by id, not delete/recreate). code-quality is a live no-op. NOTE: pr-quality shows a PRE-EXISTING file-vs-live delta on .github-private (live require_last_push_approval=true vs file false) — identical before/after this move (the origin/main file carries the same value), so the move introduces no new drift. Flagged as an out-of-scope follow-up. Depends on the companion petry-projects/.github PR (must merge first). Part of #575. Follows #576. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * fix(reviews): address review comments [skip ci-relay] --------- Co-authored-by: donpetry-bot <{}+donpetry-bot@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com> Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the actions group with 7 updates in the / directory:
6.0.26.0.3db60a41eb00b127f201c7294c529c7c599324e4e0ef7b6150516c4fa447700b4902e8ed406bcfb991212121.0.1331.0.1488.1.08.2.0Updates
actions/checkoutfrom 6.0.2 to 6.0.3Release notes
Sourced from actions/checkout's releases.
Changelog
Sourced from actions/checkout's changelog.
... (truncated)
Commits
df4cb1cUpdate changelog for v6.0.3 (#2446)1cce339Fix checkout init for SHA-256 repositories (#2439)900f221fix: expand merge commit SHA regex and add SHA-256 test cases (#2414)0c366fdUpdate changelog (#2357)Updates
petry-projects/.github-private/.github/workflows/ci-failure-analyst-reusable.ymlfrom db60a41 to 0ef7b61Commits
0ef7b61Merge branch 'main' into fix/action-sha-pinning2c7fc09chore(deps): bump anthropics/claude-code-action from 1.0.128 to 1.0.133 (#406)e040dc4chore: apply manual instructions [skip ci-relay]768d8e1fix: pin GitHub Actions to specific commit SHAs per compliance standard956b955fix(dev-lead): set git identity before commit in commit_and_push (#369)6610e8afeat(engine): in-Claude model fallback before cross-provider switch (#380)baf9ae2fix(dev-lead): expose GEMINI_API_KEY so gemini fallback actually works (#381)2d43402fix(dev-lead): centralize git identity setup; apply to fix-ci & fix-reviews (...4f9cddatest(dev-lead): runtime-build PEM markers in writer redaction test (#377)Updates
petry-projects/.github/.github/workflows/dependabot-automerge-reusable.ymlfrom 1 to 2Commits
376a4fcfeat: auto-trigger PR review when all readiness criteria are met (#323)6306793feat(concurrency): add per-repo serialized concurrency to dev-lead stubs (#322)0765a60fix(compliance): track per-workflow version tags in stub checker (#302)66c4866chore: remove claude-code-reusable.yml and update auto-rebase referencesf666f32Merge pull request #320 from petry-projects/feat/harden-scorecard-workflow9c9cdd3feat: harden scorecard workflow to report malformed YAML as findingsf88d254Merge pull request #319 from petry-projects/fix/scorecard-summary-score57c1c5efix: update aggregate score extraction key for scorecard v5.5.06fd676bMerge pull request #312 from petry-projects/fix/scorecard-workflow-v2b1b947efix: resolve jq parse error by iterating with indexUpdates
petry-projects/.github/.github/workflows/dependency-audit-reusable.ymlfrom 1 to 2Commits
376a4fcfeat: auto-trigger PR review when all readiness criteria are met (#323)6306793feat(concurrency): add per-repo serialized concurrency to dev-lead stubs (#322)0765a60fix(compliance): track per-workflow version tags in stub checker (#302)66c4866chore: remove claude-code-reusable.yml and update auto-rebase referencesf666f32Merge pull request #320 from petry-projects/feat/harden-scorecard-workflow9c9cdd3feat: harden scorecard workflow to report malformed YAML as findingsf88d254Merge pull request #319 from petry-projects/fix/scorecard-summary-score57c1c5efix: update aggregate score extraction key for scorecard v5.5.06fd676bMerge pull request #312 from petry-projects/fix/scorecard-workflow-v2b1b947efix: resolve jq parse error by iterating with indexUpdates
petry-projects/.github/.github/workflows/feature-ideation-reusable.ymlfrom 1 to 2Commits
376a4fcfeat: auto-trigger PR review when all readiness criteria are met (#323)6306793feat(concurrency): add per-repo serialized concurrency to dev-lead stubs (#322)0765a60fix(compliance): track per-workflow version tags in stub checker (#302)66c4866chore: remove claude-code-reusable.yml and update auto-rebase referencesf666f32Merge pull request #320 from petry-projects/feat/harden-scorecard-workflow9c9cdd3feat: harden scorecard workflow to report malformed YAML as findingsf88d254Merge pull request #319 from petry-projects/fix/scorecard-summary-score57c1c5efix: update aggregate score extraction key for scorecard v5.5.06fd676bMerge pull request #312 from petry-projects/fix/scorecard-workflow-v2b1b947efix: resolve jq parse error by iterating with indexUpdates
anthropics/claude-code-actionfrom 1.0.133 to 1.0.148Release notes
Sourced from anthropics/claude-code-action's releases.
... (truncated)
Commits
d5726dechore: bump Claude Code to 2.1.177 and Agent SDK to 0.3.17756fa348chore: bump Claude Code to 2.1.176 and Agent SDK to 0.3.17682d95d4Add pr-stamp-sweep review workflow (#1409)0cb4f3echore: bump Claude Code to 2.1.175 and Agent SDK to 0.3.1758551f4bfix(image-downloader): detect image type from magic bytes (#1396)eba921fdocs: fix execution file parsing example (#1297)36617bdfix(sanitizer): match attribute quotes by type to avoid mangling content (#1371)24b9156Include labels in formatContext() output for issues and PRs (#1298)9441a7ffix: clear stale claude-prompts dir before each write (#1288)b371255pin setup-bun path for post steps (#1365)Updates
SonarSource/sonarqube-scan-actionfrom 8.1.0 to 8.2.0Release notes
Sourced from SonarSource/sonarqube-scan-action's releases.
Commits
7138816SQSCANGHA-127 Rename downloaded file to .zip before extraction on Windows (#251)3581139SQSCANGHA-135 Fix scanner binaries always re-downloaded due to incompatible 4...c9d327cSQSCANGHA-84 Remove outdated wget/curl referencesb243e51SQSCANGHA-88 Deprecate the SONARCLOUD_URL env variable support375c3f5SQSCANGHA-149 Add scannerBinariesAuthHeader input for authenticated binary do...9c78323SQSCANGHA-144 Add gate jobs to QA workflows for branch protection