Skip to content

ci: add workflow that updates dependencies every 6 months#271

Draft
leahaeusel wants to merge 1 commit into
queens-py:mainfrom
leahaeusel:add-renovate-action
Draft

ci: add workflow that updates dependencies every 6 months#271
leahaeusel wants to merge 1 commit into
queens-py:mainfrom
leahaeusel:add-renovate-action

Conversation

@leahaeusel
Copy link
Copy Markdown
Member

Description and Context:
What and Why?

This PR adds a workflow that automatically generates a PR that updates our dependencies every 6 months. It uses renovate to do this.

Related Issues and Pull Requests

Interested Parties

@maxdinkel

Note: More information on the merge request procedure in QUEENS can be found in the Submit a pull request section in the CONTRIBUTING.md file.

@leahaeusel leahaeusel force-pushed the add-renovate-action branch 20 times, most recently from cb9da0b to 5e56de0 Compare January 30, 2026 15:48
Copy link
Copy Markdown
Contributor

@danielwolff1 danielwolff1 left a comment

Choose a reason for hiding this comment

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

Thanks for looking into the automatic update of dependencies, I think this will be a huge benefit to the project as a whole! 🙌 🥳

Comment thread .github/renovate.json
"extends": ["config:recommended"],
"packageRules": [
{
"matchManagers": ["pip_requirements", "conda"],
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.

Now that we are changing to pixi as dependency manager, do you think we need to rethink the renovate configuration and maybe postpone the feature until #301 is merged? I am not sure if anything will change really, since under the hood we still rely on conda and pip to resolve the packages. What makes me wonder is that with the new configuration we would most likely need to update both the compose.conda-lock.yml and the pixi.lock file. Additionally, now we explicitly list dependency versions inside our pyproject.toml and I assume they would need to be updated as well...? What do you think?

Maybe @sbrandstaeter has a more concrete idea of how applicable this still would be in connection with the new workflow 😄

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yes, we definitely need to rethink whether we will use renovate or which tool will be best for updating dependencies in the future.

This completely depends on our new dependency management (#301), which makes the current state of this PR obsolete. Sorry for not communicating that in a clearer way besides keeping the PR in draft mode 🙈

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.

no worries, this was definitely clear, this is completely on me 😬 But good that we clarified it nontheless! 😁

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 have added a list of follow-up points to #301. One of them is automatic updating. There is information on how to do that with pixi (see e.g. updating lockfile)

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.

3 participants