Skip to content

chore: Configure Renovate - #71

Merged
devparada merged 1 commit into
mainfrom
renovate/configure
Sep 4, 2026
Merged

chore: Configure Renovate#71
devparada merged 1 commit into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Sep 4, 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

  • .github/workflows/ci.yml (github-actions)
  • package.json (npm)
  • pnpm-workspace.yaml (npm)

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

What to Expect

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

fix(deps): update astro monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/astro-monorepo
  • Merge into: main
  • Upgrade @astrojs/sitemap to 3.7.4
  • Upgrade astro to 7.3.1
chore(deps): update pnpm to v11.25.0
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-11.x
  • Merge into: main
  • Upgrade pnpm to 11.25.0
fix(deps): update dependency @​lucide/astro to v1.41.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lucide-monorepo
  • Merge into: main
  • Upgrade @lucide/astro to 1.41.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.

@vercel

vercel Bot commented Sep 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
portfolio Building Building Preview Sep 4, 2026 3:45pm UTC

@devparada
devparada merged commit 1f9f91f into main Sep 4, 2026
4 checks passed
@renovate
renovate Bot deleted the renovate/configure branch September 4, 2026 15:49
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.

1 participant