Repository navigation
chore(deps): update dependency opendefensecloud/dev-kit to v3 - #145
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Coverage Report for CI Build 40195835334Coverage remained the same at 42.178%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
f322d20 to
4d8f127
Compare
## What Moves to dev-kit v3.1.0, replaces our copies of the shared workflows with dev-kit stubs, and turns on Renovate auto-approve for patch and digest PRs. Closes #132. Supersedes #145. ## Why Same setup as solution-arsenal and artifact-conduit: auto-approve only approves an unmodified, single-commit Renovate branch, and the relock workflow fixes `flake.lock` on Renovate's dev-kit and Go-version PRs so they can go green. ## Testing `make lint` passes in the dev shell, including the new `check-dev-kit-pins` and `check-go-version`. The `flake.lock` diff changes only the dev-kit entry. No Go changes, so `test` is left to CI. ## Notes for reviewers - Replaced with stubs: `update-action-pins`, `conventional-commits`, `osv-scanner`, `issues-add-labels`, `issues-add-to-project`. - The `flake.nix` dev-kit input was unpinned (default branch); it is now pinned to v3.1.0. - `golang.yaml` gets a `changes` job, so `lint`/`test` skip on PRs that touch no Go, flake or tool files and still report, as they must once they are required. - `REPO_*` settings match the live ruleset, plus `lint` and `test` as required checks. After merging, a repo admin runs `make repo-settings`; until then an auto-approved PR could merge without them. - Renovate's v3.1.1 PR will follow; it is the first run of `dev-kit-bot` here. ## 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 --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Chores** * Updated repository automation for pull requests, issue labeling, project tracking, dependency scanning, and release drafts. * Added checks for Nix changes and automated Renovate pull request handling. * Expanded backend change detection so relevant lint checks run for backend updates while avoiding unnecessary runs. * Updated development tooling and added repository settings and additional consistency checks. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
4d8f127 to
2cb8f69
Compare
|
Superseded by #153 |
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
This PR contains the following updates:
v2.2.0→v3.1.0v3.1.1Release Notes
opendefensecloud/dev-kit
v3.1.0Compare Source
Changes
v3.0.4Compare Source
Changes
v3.0.3Compare Source
Changes
v3.0.2Compare Source
Changes
v3.0.1Compare Source
Changes
v3.0.0Compare Source
Migrating from v2
v3.0.0 is breaking: the governance workflows move into dev-kit as reusable workflows, and
make repo-settingsno longer installsupdate-action-pins.yml. In each consuming repository, in order:DEV_KIT_VERSIONin the Makefile, theflake.nixinput, andsetup-nixin the workflows. With renovate-config they arrive together in onedev-kitPR; when it changesflake.nix, commitnix flake update dev-kiton the branch (its PR body says so).update-action-pins,conventional-commits,osv-scanner,issues-add-labelsandissues-add-to-projectwith the stubs from the README's "Governance workflows" section.scorecardstays a standalone workflow.REPO_STATUS_CHECKSto the names reusable workflows report,<stub job> / <called job>(e.g.update-action-pins / Check action pins,osv-scanner / scan-pr / osv-scan), then have a repo admin runmake repo-settings. Do both in the same change, or the old names stay required and never report..common.mk-configsto.gitignore— it records which shared configscommon.mkfetched.Optional:
make fmt-allonce, commit, then setDEV_KIT_FORMATTING := onbefore-include common.mk.renovate-dev-kit-lockcommits the relockedflake.lockto Renovate's dev-kit PR. It needs thedev-kit-botapp and theDEV_KIT_BOT_APP_*org secrets on the repository (currently solution-arsenal only).runs-onin your own workflows toubuntu-24.04, as dev-kit's reusable workflows now do.No stub triggers on
merge_group; see the README before enabling a merge queue.Changes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.