Skip to content

Switch Renovate to opt‑out mode (#245)#118

Open
Subramanian-K812 wants to merge 4 commits into
eclipse-score:mainfrom
qorix-group:Subramanian-K812_renovate_optout
Open

Switch Renovate to opt‑out mode (#245)#118
Subramanian-K812 wants to merge 4 commits into
eclipse-score:mainfrom
qorix-group:Subramanian-K812_renovate_optout

Conversation

@Subramanian-K812

@Subramanian-K812 Subramanian-K812 commented Jun 4, 2026

Copy link
Copy Markdown

Switch Renovate to opt-out mode in reference_integration.

Closes: eclipse-score/reference_integration#245

Comment thread .github/renovate.json5
"!eclipse-score/inc_gen_ai",
"!eclipse-score/inc_score_codegen",
// --- Self-referential: exclude the renovate config repo itself ---
"!eclipse-score/cicd-workflows",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What would happen, if this line is removed? I expect that we still want to get updates for Github Actions used within this repository.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

renovate is only updating score bazel modules. So its irrelevant here at the moment,

Comment thread .github/renovate.json5
"eclipse-score/score",
"eclipse-score/testing_tools",
"eclipse-score/toolchains_rust",
// Autodiscover repositories in the org and opt-out where needed.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I just realized there was a problem running it in more repos. It requires valid and complete lockfiles. Those don't work in all repos. Our current lockfile check does not verify completeness.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Thanks for pointing out the lockfile completeness issue. Since we’re moving to opt‑out, would you recommend we add a stricter lockfile validation step before enabling Renovate, or should we exclude repos without complete lockfiles for now?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@AlexanderLanin Just following up on my earlier note about lockfile completeness. Since we’re moving to opt‑out, I wanted to confirm the best approach:

Should we add a stricter lockfile validation step before enabling Renovate across repos?
Or would you prefer we exclude repos without complete lockfiles for now?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

@Subramanian-K812 I've added it to the infrastructure meeting agenda. In the meantime I'm trying to generate an overview of the current state.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It's not promising.

image

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

That seems weird though no? Didn't Dan add module lock error file stuff in many repos?

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

Renovate bot: change opt-in to opt-out

4 participants