Uh oh!
There was an error while loading. Please reload this page.
Bump ExecuTorch to 1.4.1 - #4434
Merged
lanluo-nvidia merged 1 commit intoAug 18, 2026
Merged
Conversation
shoumikhinforce-pushed
the
pin-executorch-release-1.4
branch
from
July 28, 2026 22:05
7b76b42 to
8002a42Compare
This was referenced Jul 28, 2026
lanluo-nvidia
left a comment
Collaborator
There was a problem hiding this comment.
@shoumikhin the change itself lgtm.
I will first merge in my build executorch-runtime wheel PR: #4398
(Waiting on @narendasan 's final review and approve)
and then we can add this on top of it.
shoumikhinforce-pushed
the
pin-executorch-release-1.4
branch
from
August 7, 2026 18:53
8002a42 to
546c7a7Compare
The pinned ExecuTorch was 1.3.1. Move it to 1.4.1, the current stable release. Every place that names the version moves together, because the Bazel pin fetches a git commit while the Python package installs a released wheel. If the two disagree, the C++ runtime and the Python package are built from different source and the mismatch only surfaces later as a serialized engine layout error. MODULE.bazel and its docker and CI copies git commit for the 1.4.1 tag the ExecuTorch build workflow pip install executorch==1.4.1 the runtime package README and pyproject same version Verified that Bazel resolves the new pin and that the fetched source is the intended release: bazel fetch @executorch//... All external dependencies for the requested targets fetched successfully fetched tree version.txt: 1.4.1
shoumikhinforce-pushed
the
pin-executorch-release-1.4
branch
from
August 18, 2026 00:32
546c7a7 to
788ed59CompareUh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
The pinned ExecuTorch version was 1.3.1. This moves it to 1.4.1, the current stable
release.
Why several files change
ExecuTorch is referenced twice in different forms. The Bazel build fetches a git commit,
and the Python runtime package installs a released wheel. If those two disagree, the C++
runtime and the Python package get built from different source, and the mismatch does not
show up until much later as a serialized engine layout error. So every place that names
the version moves together:
The comments in the docker and CI copies previously described the pin as a branch head.
They point at a release tag, so they now say so, matching
MODULE.bazel.Testing
Verified that Bazel resolves the new pin, and that the source it resolves to is the
intended release rather than some other commit: