Skip to content

Update dependency invoke to v3 #50838

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

Closed
renovate wants to merge 1 commit into from
Closed

Update dependency invoke to v3 #50838

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deps/py_dev_requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
invoke==2.2.1
invoke==3.0.3
pyyaml==6.0.3
6 changes: 3 additions & 3 deletions deps/py_dev_requirements_lock.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@
#
# bazel run //deps:py_dev_requirements.update
#
invoke==2.2.1 \
--hash=sha256:2413bc441b376e5cd3f55bb5d364f973ad8bdd7bf87e53c79de3c11bf3feecc8 \
--hash=sha256:515bf49b4a48932b79b024590348da22f39c4942dff991ad1fb8b8baea1be707
invoke==3.0.3 \

@chatgpt-codex-connector chatgpt-codex-connector Bot May 15, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Regenerate Bazel lockfile for updated invoke version

Bumping invoke here without updating MODULE.bazel.lock leaves Bazel’s resolved dependency graph stale (MODULE.bazel.lock in this commit still records invoke-2.2.1), which means CI will fail in the bazel:mod-deps check I inspected at .gitlab/build/bazel/lint.yml (bazel mod deps ... followed by git diff --exit-code). This change should include the lockfile refresh so the committed lock state matches invoke==3.0.3.

Useful? React with 👍 / 👎.

--hash=sha256:437b6a622223824380bfb4e64f612711a6b648c795f565efc8625af66fb57f0c \
--hash=sha256:f11327165e5cbb89b2ad1d88d3292b5113332c43b8553b494da435d6ec6f5053
# via -r deps/py_dev_requirements.txt
pyyaml==6.0.3 \
--hash=sha256:00c4bdeba853cc34e7dd471f16b4114f4162dc03e6b7afcc2128711f0eca823c \
Expand Down
Loading