Skip to content

chore: Configure Renovate - #28

Merged
fgm merged 2 commits into
mainfrom
renovate/configure
Sep 6, 2026
Merged

chore: Configure Renovate#28
fgm merged 2 commits into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Apr 11, 2026

Copy link
Copy Markdown
Contributor

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


Detected Package Files

  • .tool-versions (asdf)
  • .github/workflows/check-first-week.yml (github-actions)
  • .github/workflows/codeql.yml (github-actions)
  • .github/workflows/dependency-review.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • .github/workflows/scorecard.yml (github-actions)
  • .github/workflows/tests.yml (github-actions)
  • .github/workflows/update.yml (github-actions)
  • go.mod (gomod)
  • renovate.json (renovate-config)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Hopefully safe environment variables to allow users to configure.
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Pin github-action digests.
  • Schedule once a month on the first day of the month before 4 AM.
  • Run Renovate on following schedule: * 0-3 1 * *

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): update step-security/harden-runner action to v2.21.1
  • Schedule: ["* 0-3 1 * *"]
  • Branch name: renovate/step-security-harden-runner-2.x
  • Merge into: main
  • Upgrade step-security/harden-runner to e14015d583714f6e62063499dc959a02595150a1

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


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

@codecov-commenter

codecov-commenter commented Apr 11, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.82%. Comparing base (c6cc4a1) to head (ef11048).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage   98.82%   98.82%           
=======================================
  Files           4        4           
  Lines         170      170           
=======================================
  Hits          168      168           
  Misses          1        1           
  Partials        1        1           
Flag Coverage Δ
unittests 98.82% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate
renovate Bot force-pushed the renovate/configure branch from ab85ccf to 485536d Compare July 4, 2026 12:13
@fgm
fgm force-pushed the renovate/configure branch from 485536d to 466e34c Compare August 22, 2026 10:19
fgm added a commit that referenced this pull request Aug 22, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from 466e34c to 50c8278 Compare August 22, 2026 20:39
fgm added a commit that referenced this pull request Aug 23, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from 50c8278 to 6cba02f Compare August 23, 2026 12:04
fgm added a commit that referenced this pull request Aug 23, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from 6cba02f to 86f05b9 Compare August 23, 2026 16:42
fgm added a commit that referenced this pull request Aug 24, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from 86f05b9 to db2711a Compare August 24, 2026 13:17
fgm added a commit that referenced this pull request Aug 25, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from db2711a to c062f9e Compare August 25, 2026 14:54
fgm added a commit that referenced this pull request Aug 26, 2026
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from c062f9e to eadcd91 Compare August 26, 2026 13:44
renovate Bot and others added 2 commits September 6, 2026 11:30
renovate.json configures this repository for the hosted app. This example
covers the other case: one central Renovate instance driving several repos,
with a schedule per repository rather than per manager.

Not read by anything: it documents the setup for whoever runs that instance.
@fgm
fgm force-pushed the renovate/configure branch from eadcd91 to ef11048 Compare September 6, 2026 09:30
@fgm
fgm merged commit ef11048 into main Sep 6, 2026
7 checks passed
@fgm
fgm deleted the renovate/configure branch September 6, 2026 10:20
@fgm fgm mentioned this pull request Sep 6, 2026
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants