Repository navigation
Conversation
Picks up the issues-add-to-project fix (dev-kit#53). The reusable
workflow asked for `contents: read` while our stub calls it with
`permissions: {}`, so the run failed at startup on every opened PR
since the move to v3 and nothing landed on the project board.
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
cbrgm
marked this pull request as ready for review
October 13, 2026 13:27
Coverage Report for CI Build 38402349487Coverage increased (+0.03%) to 78.83%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions4 previously-covered lines in 2 files lost coverage.
Coverage Stats
💛 - Coveralls |
Contributor
Author
|
@AlexHardAtWork is working on some other fixes here, so maybe its worth waiting until his changes are done and bump straight to v3.0.4 if needed. |
Contributor
Author
|
Closing this one since we were straight away update to 3.0.4 |
4 tasks done
AlexHardAtWork
added a commit
that referenced
this pull request
Oct 15, 2026
## What Moves every dev-kit pin from v3.0.2 to v3.1.0: workflow stubs, `Makefile`, `flake.nix`, `flake.lock`. Supersedes #867 (v3.0.3). ## Why v3.1.0's `renovate-dev-kit-lock` also relocks `go-overlay` on `renovate/go-version` (dev-kit#56). That is what #862 lacks: Go 1.27.2 isn't in the locked overlay, so every nix job fails evaluating the shell. Picks up v3.0.3/v3.0.4 on the way: the `issues-*` reusable workflows no longer ask for permissions the stubs don't grant (dev-kit#53, #54). ## Testing `make check-dev-kit-pins` agrees on v3.1.0; the `flake.lock` diff is the dev-kit node only. Commit hooks (`fmt`, `lint`) pass. ## Notes for reviewers - After merge, the plan is to rebase #862 (remove its `automerge` label first). Expect a `dev-kit-bot` commit relocking `go-overlay`, then green CI. Auto-approve will reject that PR because it now has two commits; merge it by hand. - No stub changes needed: v3.0.4 and v3.1.0 add no inputs or permissions that the stubs have to pass. ## Checklist - [x] Tests added/updated, or confirmed that no tests are required - [x] No breaking changes, or upgrade path documented above - [x] Readable commit history (squashed and cleaned up as desired) - [x] AI code review considered and comments resolved <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated the project’s development and automation tooling to newer shared versions. * No changes to user-facing features or application behavior. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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
3 participants
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.
What
Moves every dev-kit pin from v3.0.2 to v3.0.3: workflow stubs,
Makefile,flake.nix,flake.lock. Same shape as 5c18d20.Why
Picks up opendefensecloud/dev-kit#53. Since the move to v3,
Add issues to projectfails at startup on every opened PR -> https://github.com/opendefensecloud/solution-arsenal/actions/runs/38392325299The reusable workflow asked for more than our stub (
permissions: {}) hands down. v3.0.3 drops the request, the stub stays as it is.v3.0.2...v3.0.3 contains only that one fix.
Testing
flake.lockrelocked withnix flake update dev-kit(nix in a container, no local install).The real test is this PR itself: opening it triggers
Add issues to projectwith the new pin.Checklist