Repository navigation
chore(deps): update dependency opendefensecloud/dev-kit to v3 - #109
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
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.
This PR contains the following updates:
v2.2.0→v3.0.0v3.1.0(+4)Release Notes
opendefensecloud/dev-kit
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.