Skip to content

chore: Configure Renovate#16

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure
Open

chore: Configure Renovate#16
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Mar 1, 2026

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.


Detected Package Files

  • .github/workflows/check-semantic-pull-request.yml (github-actions)
  • .github/workflows/check-skill-sync.yml (github-actions)
  • .github/workflows/ci.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • package.json (npm)
  • .nvmrc (nvm)

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

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


What to Expect

With your current configuration, Renovate will create 12 Pull Requests:

chore(deps): update amannn/action-semantic-pull-request digest to ac7e3fc
  • Schedule: ["at any time"]
  • Branch name: renovate/amannn-action-semantic-pull-request-digest
  • Merge into: main
  • Upgrade amannn/action-semantic-pull-request to ac7e3fc035c47465748bbcb1a822c1583cf79bbc
chore(deps): update dependency @​types/node to v22.19.15
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x-lockfile
  • Merge into: main
  • Upgrade @types/node to 22.19.15
chore(deps): update dependency conventional-changelog-conventionalcommits to v9.3.1
chore(deps): update dependency oxfmt to v0.43.0
  • Schedule: ["at any time"]
  • Branch name: renovate/oxfmt-0.x
  • Merge into: main
  • Upgrade oxfmt to 0.43.0
chore(deps): update dependency oxlint to v1.58.0
  • Schedule: ["at any time"]
  • Branch name: renovate/oxlint-monorepo
  • Merge into: main
  • Upgrade oxlint to 1.58.0
chore(deps): update dependency yocto-spinner to v1.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/yocto-spinner-1.x-lockfile
  • Merge into: main
  • Upgrade yocto-spinner to 1.1.0
chore(deps): update actions/checkout action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-6.x
  • Merge into: main
  • Upgrade actions/checkout to v6
chore(deps): update actions/setup-node action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-6.x
  • Merge into: main
  • Upgrade actions/setup-node to v6
chore(deps): update dependency @​types/node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade @types/node to ^24.0.0
chore(deps): update dependency lefthook to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/lefthook-2.x
  • Merge into: main
  • Upgrade lefthook to ^2.0.0
chore(deps): update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
chore(deps): update dependency vitest to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade vitest to ^4.0.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.


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

Copy link
Copy Markdown

@doistbot-app doistbot-app bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR introduces the initial configuration for Renovate to automate dependency management, which will help keep GitHub Actions and npm packages up-to-date with minimal manual effort. While the integration is a great addition for long-term maintainability, the new configuration file currently uses 2-space indentation instead of the 4-space standard defined in the project's Biome settings.

Share FeedbackReview Logs

Comment thread renovate.json
@@ -0,0 +1,6 @@
{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Inconsistent indentation (2 spaces instead of 4). The repository standard for JSON files, as defined in biome.json and used across the codebase (e.g., package.json, tsconfig.json), is 4-space indentation. This file should be updated to use 4 spaces to ensure consistency and avoid CI failures during the npm run check step.

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.

0 participants