Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #17

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Configure Renovate #17

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 28, 2022

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/main.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
  • Show all Merge Confidence badges for pull requests.
  • Use semantic prefixes for commit messages and PR titles.
  • 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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.
  • Set semantic commit type based on advanced rules
  • Presets that harden security for shared GitHub Action Workflows
  • Always widen peerDependencies and engines, while other types like dependencies, devDependencies are update-lockfile.
  • Assign 📦 deps and 🤖 bot labels, and for major updates ⚠️ major
  • Opt-in to refresh lock files once in a while
  • Update CI images to use the latest LTS of Node.js
  • Pin TypeScript to the same version used by @sanity/pkg-utils and @sanity/tsdoc
  • Group various lint packages together.
  • Group PostCSS packages together.
  • Group all updates except major into its own PR, when possible.
  • Deps that are noisy and don't need to be automatically maintained
  • Workaround packages that are Pure ESM directly, or have started using transitive dependencies that are.
  • Workaround how babel-plugin-react-compiler is publishing experimental versions on the latest tag, without this workaround renovate will downgrade the version to 0.0.0
  • Dedupe lockfiles after updates for npm, pnpm, and yarn.
  • Use curated presets maintained by Sanity. See docs for advanced usage.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to .github/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 14 Pull Requests:

chore(deps): update non-major
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update actions/setup-node action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-4.x
  • Merge into: main
  • Upgrade actions/setup-node to v4
chore(deps): update commitlint monorepo to v18 (major)
chore(deps): update commitlint monorepo to v19 (major)
chore(deps): update dependency @​sanity/pkg-utils to v3
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/sanity-pkg-utils-3.x
  • Merge into: main
  • Upgrade @sanity/pkg-utils to ^3.3.8
chore(deps): update dependency @​sanity/pkg-utils to v4
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/sanity-pkg-utils-4.x
  • Merge into: main
  • Upgrade @sanity/pkg-utils to ^4.4.4
chore(deps): update dependency @​sanity/pkg-utils to v5
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/sanity-pkg-utils-5.x
  • Merge into: main
  • Upgrade @sanity/pkg-utils to ^5.1.12
chore(deps): update dependency @​sanity/pkg-utils to v6
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/sanity-pkg-utils-6.x
  • Merge into: main
  • Upgrade @sanity/pkg-utils to ^6.11.2
chore(deps): update dependency @​sanity/plugin-kit to v4
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/sanity-plugin-kit-4.x
  • Merge into: main
  • Upgrade @sanity/plugin-kit to ^4.0.18
chore(deps): update dependency @​sanity/semantic-release-preset to v5
  • Schedule: ["before 3am on the first day of the month"]
  • Branch name: renovate/major-5-semantic-release
  • Merge into: main
  • Upgrade @sanity/semantic-release-preset to ^5.0.0
chore(deps): update linters to v7 (major)
chore(deps): update linters to v8 (major)
chore(deps): lock file maintenance
  • Schedule: ["every 12 months on the first day of the month"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 Branch 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 has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate bot force-pushed the renovate/configure branch from 81325c5 to c1d0612 Compare September 9, 2024 11:30
@renovate renovate bot force-pushed the renovate/configure branch from c1d0612 to bd653d4 Compare September 27, 2024 11:31
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