Skip to content

chore: Configure Renovate - #85

Open
renovate[bot] wants to merge 4 commits into
mainfrom
renovate/configure
Open

chore: Configure Renovate#85
renovate[bot] wants to merge 4 commits into
mainfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Aug 24, 2026

Copy link
Copy Markdown

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

  • 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 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
  • If Renovate detects semantic commits, it will use semantic commit type chore for all commits.
  • Run Renovate on following schedule: * 6-10 * * 1

What to Expect

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

chore(deps): update dependency @​capacitor/splash-screen to v8.0.2
chore(deps): update dev-tools
  • Schedule: ["* 6-10 * * 1"]
  • Branch name: renovate/dev-tools
  • Merge into: main
  • Upgrade @eslint/js to 9.39.5
  • Upgrade eslint to 9.39.5
  • Upgrade typescript-eslint to 8.67.0
chore(deps): update angular
chore(deps): update testing
chore(deps): update dependency typescript to v7
  • Schedule: ["* 6-10 1 * *"]
  • Branch name: renovate/major-angular
  • Merge into: main
  • Upgrade typescript to ~7.0.0
chore(deps): update dev-tools to v10
  • Schedule: ["* 6-10 * * 1"]
  • Branch name: renovate/major-dev-tools
  • Merge into: main
  • Upgrade @eslint/js to ^10.0.0
  • Upgrade eslint to ^10.0.0
chore(deps): update testing (major)

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

Comment thread renovate.json
"config:recommended",
":semanticCommitTypeAll(chore)"
],
"timezone": "America/New_York",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Are we planning to add timezone to all the other repos? Right now, we don't have this value configured.

Comment thread renovate.json
],
"timezone": "America/New_York",
"minimumReleaseAge": "3 days",
"schedule": ["* 6-10 * * 1"],

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Let's add a comment of what this is supposed to be.

Comment thread renovate.json
],
"groupName": "angular",
"schedule": ["* 6-10 1 * *"]
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

The preview shows renovate/major-angular bumping TypeScript to v7 by itself — majors get split out of groups — and Angular 22 peers on typescript >=6.0 <6.1, so that one would break the build. This holds TS back until the Angular major catches up.

We'll also need to add this to the Conference apps.

Suggested change
},
},
{
"matchPackageNames": ["typescript"],
"allowedVersions": "<7.0.0",
"description": "Angular 22's compiler-cli peers on typescript >=6.0 <6.1; raise this ceiling when moving to Angular 23"
},

Comment thread renovate.json
"tslib"
],
"groupName": "angular",
"schedule": ["* 6-10 1 * *"]

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Let's add a comment of what this is supposed to be.

Comment thread renovate.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.

It would be great to add a small CI file to verify that nothing breaks with the updates. For now, something like the docs site with just a check that npm run lint, npm run test and npm run build pass without issues.

Comment thread renovate.json
"@types/jasmine"
],
"groupName": "testing"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

karma-jasmine-html-reporter@2 peers on jasmine-core ^4 || ^5, and there's no 3.x to bump it to — so the major-testing PR would take jasmine to 7 and leave the reporter behind. Capping until the reporter catches up.

Suggested change
},
},
{
"matchPackageNames": ["jasmine-core", "@types/jasmine"],
"allowedVersions": "<6.0.0",
"description": "karma-jasmine-html-reporter@2 peers on jasmine-core ^4 || ^5; raise this ceiling when it supports a newer jasmine"
},

Comment thread renovate.json
"minimumReleaseAge": "3 days",
"schedule": ["* 6-10 * * 1"],
"semanticCommits": "enabled",
"dependencyDashboard": true,

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This is already enabled with config:recommended.

Suggested change
"dependencyDashboard": true,

Comment thread .github/CODEOWNERS
# In each subsection folders are ordered first by depth, then alphabetically.
# This should make it easy to add new rules without breaking existing ones.

* @ionic-team/framework No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Can we add a new line?

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.

2 participants