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 #15618

Merged
merged 10 commits into from
Mar 5, 2023
Merged

Configure Renovate #15618

merged 10 commits into from
Mar 5, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 27, 2023

Mend Renovate

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

  • package.json (npm)

Configuration

🔡 Renovate has detected a custom config for this PR. Feel free to ask for help if you have any doubts and would like it reviewed.

Important: Now that this branch is edited, Renovate can't rebase it from the base branch any more. If you make changes to the base branch that could impact this onboarding PR, please merge them manually.

What to Expect

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

Pin dependencies
Pin dependencies
Pin dependencies
Update dependency @​rollup/plugin-babel to ^5.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-babel-5.x
  • Merge into: dev
  • Upgrade @rollup/plugin-babel to ^5.3.0
Update dependency @​types/chromecast-caf-receiver to v5.0.15
Update Yarn to v3.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/yarn-monorepo
  • Merge into: dev
  • Upgrade yarn to 3.4.1
Update dependency @​rollup/plugin-json to ^4.1.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-json-4.x
  • Merge into: dev
  • Upgrade @rollup/plugin-json to ^4.1.0
Update dependency @​web/dev-server-rollup to ^0.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/web-dev-server-rollup-0.x
  • Merge into: dev
  • Upgrade @web/dev-server-rollup to ^0.3.0
Update dependency chart.js to ^3.9.1
  • Schedule: ["at any time"]
  • Branch name: renovate/chart.js-3.x
  • Merge into: dev
  • Upgrade chart.js to ^3.9.1
Update dependency webpack to v5.75.0
  • Schedule: ["at any time"]
  • Branch name: renovate/webpack-5.x
  • Merge into: dev
  • Upgrade webpack to =5.75.0
Update dependency @​rollup/plugin-babel to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-babel-6.x
  • Merge into: dev
  • Upgrade @rollup/plugin-babel to ^6.0.0
Update dependency @​rollup/plugin-commonjs to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-commonjs-24.x
  • Merge into: dev
  • Upgrade @rollup/plugin-commonjs to ^24.0.0
Update dependency @​rollup/plugin-json to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-json-6.x
  • Merge into: dev
  • Upgrade @rollup/plugin-json to ^6.0.0
Update dependency @​rollup/plugin-node-resolve to v15
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-node-resolve-15.x
  • Merge into: dev
  • Upgrade @rollup/plugin-node-resolve to ^15.0.0
Update dependency @​rollup/plugin-replace to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-replace-5.x
  • Merge into: dev
  • Upgrade @rollup/plugin-replace to ^5.0.0
Update dependency @​types/chromecast-caf-receiver to v6
Update dependency chart.js to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/chart.js-4.x
  • Merge into: dev
  • Upgrade chart.js to ^4.0.0
Update dependency glob to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/glob-9.x
  • Merge into: dev
  • Upgrade glob to ^9.0.0
Update dependency rollup to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-3.x
  • Merge into: dev
  • Upgrade rollup to ^3.0.0
Update dependency rollup-plugin-terser to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-terser-7.x
  • Merge into: dev
  • Upgrade rollup-plugin-terser to ^7.0.0
Lock file maintenance
  • Schedule: ["on the 19th day of the month"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: dev
  • Regenerate lock files to use latest dependency versions

❓ 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. View repository job log here.

@frenck
Copy link
Member

frenck commented Feb 27, 2023

Let's make sure we configure renovate to only act on the npm packages (and leave the rest up to dependabot).

@steverep steverep self-assigned this Feb 27, 2023
@steverep steverep marked this pull request as draft February 27, 2023 20:35
@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from 374fe5b to af1a895 Compare March 2, 2023 09:05
Comment on lines +4 to +5
":automergeLinters",
":automergeTypes",
Copy link
Member

Choose a reason for hiding this comment

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

Automerge sounds like something we should never ever allow or do.

Copy link
Member

Choose a reason for hiding this comment

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

  1. This is very conservative and only permits it for ESLint, Prettier, and @types/* packages. If the CI passes, there's no reason not to merge. That's what any human would do.
  2. It won't actually allow it anyway because the PR still requires approval per the branch protection rule. Without changes on GitHub, all it will do is effectively check the box on the PR.

Renovate has a decent discussion of the automerge feature on their website.

Copy link
Member

@frenck frenck Mar 5, 2023

Choose a reason for hiding this comment

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

This was a serious review comment which you just declined, dismissed any further discussion, added yourself, self approved and now merged.

Please revert this asap.

Copy link
Member

@frenck frenck Mar 5, 2023

Choose a reason for hiding this comment

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

That's what any human would do.

I hope for sure, that is not what any reviewer (or you) does. At least the upstream changes should be reviewed. Something renovate will not do for you, as it is not an human.

../Frenck

Copy link
Member

Choose a reason for hiding this comment

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

I hope for sure, that is not what any reviewer (or you) does. At least the upstream changes should be reviewed. Something renovate will not do for you, as it is not an human.

I did not intend to imply that the release notes should not be reviewed. I certainly do that every time. I simply meant that in those particular cases, the CI lint is all that is needed in terms of testing.

Again, I included those rules in a way that was simply meant as an extra click time saver on a small subset of very low risk packages. No actual automatic merging was configured.

In any case, I removed all mentions of automerge in #15743.

@steverep
Copy link
Member

steverep commented Mar 5, 2023

Okay I think this is a good config to start with. Other than the deduplicating and "automerge" (which won't actually automerge) per my comment above, it will virtually be the same as dependabot except:

  • To protect against botched releases that are pulled from NPM or quickly patched, it waits 3 days before raising a PR
  • Pins all versions - HA really has no need for or gains from specified ranges
  • Enables monthly "lock file maintenance", which just updates sub-dependencies per their semver rules (right now their just locked to whatever the current version was at the time of install)
  • No longer ignoring rollup since everything else is mostly updated

@steverep steverep marked this pull request as ready for review March 5, 2023 00:23
@steverep
Copy link
Member

steverep commented Mar 5, 2023

Merging to make sure this behaves like I expect. We can certainly follow up with changes.

@steverep steverep merged commit be909d0 into dev Mar 5, 2023
@steverep steverep deleted the renovate/configure branch March 5, 2023 01:52
@ludeeus
Copy link
Member

ludeeus commented Mar 5, 2023

You should not have merged this. While you did not open the initial PR, the initial PR does not exist and all changes are made by you.

@frenck
Copy link
Member

frenck commented Mar 5, 2023

Agree this must be reverted asap. The auto merge rules imho are a big no-go.

My review comment above has just been dismissed an you just merged your own in, without any further discussion or consensus.

frenck added a commit that referenced this pull request Mar 5, 2023
"group:monorepos",
"group:recommended",
"npm:unpublishSafe",
"workarounds:all"
Copy link
Member

Choose a reason for hiding this comment

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

I think this needs to be more specific, to prevent future (possibly unwanted) workarounds to just being blatantly accepted.

Copy link
Member

Choose a reason for hiding this comment

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

Very well. I left it there as it's part of their base config. None of the workarounds are actually relevant to this repo.

I removed it in #15743.

ludeeus pushed a commit that referenced this pull request Mar 5, 2023
Revert "Configure Renovate (#15618)"

This reverts commit be909d0.
@renovate
Copy link
Contributor Author

renovate bot commented Mar 5, 2023

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

@steverep steverep mentioned this pull request Mar 5, 2023
9 tasks
@steverep
Copy link
Member

steverep commented Mar 5, 2023

In retrospect I should not have jumped the gun to merge. I had some time to devote to this last night and was simply eager to verify some of the configured functionality worked as expected (including automerge) before stating anything that wasn't actually correct.

I meant no disrespect and had no malicious intent to dismiss or decline feedback. I don't operate that way. I intended to follow up as I stated.

@frenck
Copy link
Member

frenck commented Mar 5, 2023

We know you mean well 👍

Thanks for pushing this anyways, as I think this will be a good addition 👍

../Frenck

@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants