renovate-configs

Author	SHA1	Message	Date
t.behrendt	b94e47dc0a	feat(actions): allow automege of certain actions CI / Test (action.json) (pull_request) Successful in 11s Details CI / Test (common.json) (pull_request) Successful in 11s Details CI / Test (docker-compose.json) (pull_request) Successful in 10s Details CI / Test (helm.json) (pull_request) Successful in 11s Details CI / Test (k8s.json) (pull_request) Successful in 11s Details CI / Test (bun-npm.json) (pull_request) Successful in 1m37s Details	2026-06-20 19:09:45 +02:00
t.behrendt	7a4f5cb141	feat: ignore cooldown for internal deps (#32 ) CD / Release (push) Successful in 15s Details Ignoring min release age for any internal deps and have every rule extend the common package. Reviewed-on: #32 Co-authored-by: Timo Behrendt <t.behrendt@t00n.de> Co-committed-by: Timo Behrendt <t.behrendt@t00n.de>	2026-02-08 20:01:34 +01:00
t.behrendt	4bc8c6e40f	feat: pin digest of GitHub action updates (#2 ) CD / Release (push) Successful in 5s Details We always want to pin GitHub actions to a digest, to avoid attack vectors where existing tags are being re-used and their implementation replaced with malicious code. As described in [renovate's documentation](https://docs.renovatebot.com/modules/manager/github-actions/#digest-pinning-and-updating), adding the "helpers:pinGitHubActionDigests" to the extends automatically forces renovate to always pin digests. Reviewed-on: #2 Reviewed-by: branch-buddy <branch-buddy@t00n.de> Co-authored-by: Timo Behrendt <t.behrendt@t00n.de> Co-committed-by: Timo Behrendt <t.behrendt@t00n.de>	2025-10-08 18:54:50 +02:00
t.behrendt	82e5e832f8	feat: migrate existing configs (#1 ) CD / Release (push) Successful in 6s Details Reviewed-on: #1 Reviewed-by: branch-buddy <branch-buddy@t00n.de> Co-authored-by: Timo Behrendt <t.behrendt@t00n.de> Co-committed-by: Timo Behrendt <t.behrendt@t00n.de>	2025-10-08 18:46:12 +02:00

4 Commits