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.

Sign up for GitHub

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

Jump to bottom

Monthly upgrades for venv lockfile #22041

Open
jwnimmer-tri opened this issue Oct 15, 2024 · 0 comments
Open

Monthly upgrades for venv lockfile #22041

jwnimmer-tri opened this issue Oct 15, 2024 · 0 comments
Assignees
@mwoehlke-kitware @BetsyMcPhail
Labels
component: distribution Nightly binaries, monthly releases, docker, installation priority: medium type: feature request

Comments

@jwnimmer-tri
Copy link
Collaborator

jwnimmer-tri commented Oct 15, 2024 •
edited
Loading

As follow-up work related to #22036, as part of our semi-automated-monthly-upgrades process the Drake maintainer doing the monthly upgrade should be running venv_upgrade to re-pin the requirements lockfiles.

This is slightly subtle because the venv_upgrade program is a per-platform tool. An Ubuntu developer cannot necessarily run it for macOS upgrades. Possibly that is only a theoretical problem, however, and running it on Ubuntu to re-lock macOS would be safe, in practice.

It's OK to start with just a manual reminder sans automation, if that is better.

This is part of the #8392 epic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mwoehlke-kitware mwoehlke-kitware

@BetsyMcPhail BetsyMcPhail

Labels
component: distribution Nightly binaries, monthly releases, docker, installation priority: medium type: feature request
Projects
build system, continuous integration, distribution
Status: To do
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mwoehlke-kitware @BetsyMcPhail @jwnimmer-tri