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

devops: configure renovate #52

Merged
merged 3 commits into from
Nov 20, 2024
Merged

devops: configure renovate #52

merged 3 commits into from
Nov 20, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 20, 2024

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/deploy.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • ct-web-lit/package.json (npm)
  • ct-web/package.json (npm)
  • package.json (npm)
  • playwright-ct-web/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.
  • 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.

🔡 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 dependency vite to v5 [security]
  • Branch name: renovate/npm-vite-vulnerability
  • Merge into: master
  • Upgrade vite to ^5.0.0
chore(deps): update dependency typescript to ^5.6.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-5.x
  • Merge into: master
  • Upgrade typescript to ^5.6.3
chore(deps): update node.js to >=16.20.2
  • Schedule: ["at any time"]
  • Branch name: renovate/node-16.x
  • Merge into: master
  • Upgrade node to >=16.20.2
chore(deps): update node.js to >=18.20.5
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x
  • Merge into: master
  • Upgrade node to >=18.20.5
chore(deps): update pnpm to >=7.33.7
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-7.x
  • Merge into: master
  • Upgrade pnpm to >=7.33.7
fix(deps): update dependency lit to ^2.8.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lit-2.x
  • Merge into: master
  • Upgrade lit to ^2.8.0
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: master
  • 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: master
  • Upgrade actions/setup-node to v4
chore(deps): update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: master
  • Upgrade actions/upload-artifact to v4
chore(deps): update node.js to v22
  • Schedule: ["at any time"]
  • Branch name: renovate/node-22.x
  • Merge into: master
  • Upgrade node to >=22.11.0
chore(deps): update pnpm to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/pnpm-9.x
  • Merge into: master
  • Upgrade pnpm to >=9.14.2
fix(deps): update dependency lit to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/lit-3.x
  • Merge into: master
  • Upgrade lit to ^3.2.1

🚸 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 was generated by Mend Renovate. View the repository job log.

@sand4rt sand4rt changed the title chore: Configure Renovate devops: configure renovate Nov 20, 2024
@sand4rt
Copy link
Owner

sand4rt commented Nov 20, 2024

@jan-molak i've updated and released the new versions. Would you like to setup renovate/auto-releases in a PR?

Sure, I'd be happy to help out!

I tried Dependabot and Greenkeeper and finally settled on Renovate, as it was the only one that worked correctly with mono-repos.

We'll need to:
enable the Renovate GitHub App for sand4rt/playwright-ct-web via https://github.com/apps/renovate
add a .github/renovate.json config file, like the one here (note the automerge option) - https://github.com/serenity-js/serenity-js-playwright-ct-web-components-template/blob/main/.github/renovate.json
if the release process is automated, we can enable auto-merge. If it's not automated, we could look into automating the release.

@sand4rt sand4rt merged commit 016c1aa into master Nov 20, 2024
3 checks passed
@sand4rt sand4rt deleted the renovate/configure branch November 20, 2024 13:42
@jan-molak jan-molak mentioned this pull request Nov 21, 2024
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