Skip to content

chore(deps): update dependency opendefensecloud/dev-kit to v3 - #145

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-dev-kit
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-dev-kit

Conversation

@renovate

@renovate renovate Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change Pending
opendefensecloud/dev-kit major v2.2.0 → v3.1.0 v3.1.1

Release Notes

opendefensecloud/dev-kit

v3.1.0

Compare Source

Changes

v3.0.4

Compare Source

Changes

v3.0.3

Compare Source

Changes

  • fix(issues-add-to-project): request no token permissions @​cbrgm (#​53)

v3.0.2

Compare Source

Changes

v3.0.1

Compare Source

Changes

v3.0.0

Compare Source

Migrating from v2

v3.0.0 is breaking: the governance workflows move into dev-kit as reusable workflows, and make repo-settings no longer installs update-action-pins.yml. In each consuming repository, in order:

  1. Bump all three dev-kit pins to v3.0.0 — DEV_KIT_VERSION in the Makefile, the flake.nix input, and setup-nix in the workflows. With renovate-config they arrive together in one dev-kit PR; when it changes flake.nix, commit nix flake update dev-kit on the branch (its PR body says so).
  2. Replace the local copies of update-action-pins, conventional-commits, osv-scanner, issues-add-labels and issues-add-to-project with the stubs from the README's "Governance workflows" section. scorecard stays a standalone workflow.
  3. Update REPO_STATUS_CHECKS to 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 run make repo-settings. Do both in the same change, or the old names stay required and never report.
  4. Add .common.mk-configs to .gitignore — it records which shared configs common.mk fetched.

Optional:

  • Shared formatting is opt-in: run make fmt-all once, commit, then set DEV_KIT_FORMATTING := on before -include common.mk.
  • renovate-dev-kit-lock commits the relocked flake.lock to Renovate's dev-kit PR. It needs the dev-kit-bot app and the DEV_KIT_BOT_APP_* org secrets on the repository (currently solution-arsenal only).
  • Pin runs-on in your own workflows to ubuntu-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)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added ok-to-e2e ok-to-helm PR is allowed to build an publish helm chart ok-to-image PR is allowed to run container build labels Oct 17, 2026
@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: dfd498b2-5a64-40c5-8274-1b44afa1dd03

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coveralls

coveralls commented Oct 17, 2026 •

Copy link
Copy Markdown

Coverage Report for CI Build 40195835334

Coverage remained the same at 42.178%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 505
Covered Lines: 213
Line Coverage: 42.18%
Coverage Strength: 1.32 hits per line

💛 - Coveralls

@renovate
renovate Bot force-pushed the renovate/major-dev-kit branch 6 times, most recently from f322d20 to 4d8f127 Compare October 25, 2026 13:02
@AlexHardAtWork AlexHardAtWork mentioned this pull request Oct 26, 2026
4 tasks done
AlexHardAtWork added a commit that referenced this pull request Oct 29, 2026
## 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 -->
@renovate
renovate Bot force-pushed the renovate/major-dev-kit branch from 4d8f127 to 2cb8f69 Compare October 29, 2026 09:51
@AlexHardAtWork

Copy link
Copy Markdown
Contributor

Superseded by #153

@renovate

renovate Bot commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/major-dev-kit branch October 29, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-e2e ok-to-helm PR is allowed to build an publish helm chart ok-to-image PR is allowed to run container build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants