Skip to content

Configure Renovate#44

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

Configure Renovate#44
renovate[bot] wants to merge 1 commit intomainfrom
renovate/configure

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Apr 2, 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/e2e-tests.yml (github-actions)
  • .github/workflows/unit-tests.yml (github-actions)
  • .github/workflows/version-or-publish.yml (github-actions)
  • package.json (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 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 18 Pull Requests:

Update astro monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/astro-monorepo
  • Merge into: main
  • Upgrade @astrojs/mdx to 3.1.9
  • Upgrade astro to 4.16.19
Update dependency vitest to v2.1.9
  • Schedule: ["at any time"]
  • Branch name: renovate/vitest-monorepo
  • Merge into: main
  • Upgrade vitest to 2.1.9
Update dependency @​changesets/cli to v2.30.0
  • Schedule: ["at any time"]
  • Branch name: renovate/changesets-cli-2.x-lockfile
  • Merge into: main
  • Upgrade @changesets/cli to 2.30.0
Update dependency @​playwright/test to v1.59.1
  • Schedule: ["at any time"]
  • Branch name: renovate/playwright-monorepo
  • Merge into: main
  • Upgrade @playwright/test to 1.59.1
Update dependency astro-expressive-code to ^0.41.0
  • Schedule: ["at any time"]
  • Branch name: renovate/astro-expressive-code-0.x
  • Merge into: main
  • Upgrade astro-expressive-code to ^0.41.0
Update dependency prettier to v3.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-3.x-lockfile
  • Merge into: main
  • Upgrade prettier to 3.8.1
Update dependency typescript to v5.9.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x-lockfile
  • Merge into: main
  • Upgrade typescript to 5.9.3
Update pnpm to v9.15.9
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-9.x
  • Merge into: main
  • Upgrade pnpm to 9.15.9
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
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
Update astro monorepo (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-astro-monorepo
  • Merge into: main
  • Upgrade @astrojs/mdx to ^5.0.0
  • Upgrade astro to ^6.0.0
Update daun/playwright-report-summary action to v3
Update dependency jsdom to v29
  • Schedule: ["at any time"]
  • Branch name: renovate/jsdom-29.x
  • Merge into: main
  • Upgrade jsdom to ^29.0.0
Update dependency node to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/node-24.x
  • Merge into: main
  • Upgrade node to 24
Update dependency typescript to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-6.x
  • Merge into: main
  • Upgrade typescript to ^6.0.0
Update dependency vitest to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-vitest-monorepo
  • Merge into: main
  • Upgrade vitest to ^4.0.0
Update pnpm to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-10.x
  • Merge into: main
  • Upgrade pnpm to 10.33.0
Update pnpm/action-setup action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-action-setup-5.x
  • Merge into: main
  • Upgrade pnpm/action-setup to v5

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

@netlify
Copy link
Copy Markdown

netlify bot commented Apr 2, 2026

Deploy Preview for scrollmirror ready!

Name Link
🔨 Latest commit 2441f48
🔍 Latest deploy log https://app.netlify.com/projects/scrollmirror/deploys/69ceaf22756f80000843821a
😎 Deploy Preview https://deploy-preview-44--scrollmirror.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Apr 2, 2026

⚠️ No Changeset found

Latest commit: 2441f48

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@hirasso hirasso closed this Apr 2, 2026
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