-
Notifications
You must be signed in to change notification settings - Fork 656
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.
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
Release tracker - 3.2.0 #19641
Comments
New release date target: Feb 10, instead of Feb 17. |
We've updated the downstream shark-ai packages to use |
Release candidate install instructions, including the downstream shark-ai packages: pip install \
--find-links https://github.com/nod-ai/shark-ai/releases/expanded_assets/dev-wheels \
shortfin[apps]==3.2.0rc20250207 \
sharktank==3.2.0rc20250207
pip install \
--find-links https://iree.dev/pip-release-links.html \
iree-base-compiler==3.2.0rc20250206 \
iree-base-runtime==3.2.0rc20250206 \
iree-turbine==3.2.0rc20250205 Then check what was installed: pip freeze | grep -E 'iree|shark|shortfin'
iree-base-compiler==3.2.0rc20250206
iree-base-runtime==3.2.0rc20250206
iree-turbine==3.2.0rc20250205
sharktank==3.2.0rc20250207
shortfin==3.2.0rc20250207 Note: we could also use iree-turbine==3.2.0rc20250207 to pick up a few more changes there. |
For future releases, I hope to reduce those instructions to a single |
Seems like to use shortfin with the above commands, more dependencies need to be installed:
|
Ah, let me amend the instructions then: install |
Possible release blocking regression reported downstream: nod-ai/shark-ai#934. Waiting for more information to determine the impact. We could release IREE + iree-turbine 3.2.0 and then follow with a 3.2.1 patch release for downstream shark-ai to use in its own 3.2.0. Should know more by Monday. (Then for future releases we can also establish more of a process for branching, vetting release candidates, and incorporating feedback from downstream users/projects) |
New plan this morning is to not block the release on that issue (matching IREE issue: #19948). Might add to a list of known issues in one or both projects. I'll start the release rollout. |
https://github.com/iree-org/iree/releases/tag/v3.2.0 is now published and pushed to pypi. Next up:
|
All packages are pushed to pypi and all releases are published:
Working on process documentation updates next. |
See the 3.2.0 release tracker at #19641 and published release at https://github.com/iree-org/iree/releases/tag/v3.2.0.
See the 3.2.0 release tracker at iree-org/iree#19641 and published release at https://github.com/iree-org/iree-turbine/releases/tag/v3.2.0.
See the 3.2.0 release tracker at iree-org/iree#19641 and published release at https://github.com/nod-ai/shark-ai/releases/tag/v3.2.0.
Overview
Our previous stable release was cut on 2025-01-07: https://github.com/iree-org/iree/releases/tag/v3.1.0. We aim for roughly one stable release every 6 weeks, which will be around
2025-02-172025-02-10. This issue tracks the release process for the next release.Release process docs:
Release checklist:
experimental
in.github/workflows/build_package.yml
like macOS and Windows packages.iree-turbine
and push similar package updates to PyPIRelease notes
Candidate: https://github.com/iree-org/iree/releases/tag/iree-3.2.0rc20250206
Commit range
main
: v3.1.0...main3.2.0rc20250206
: v3.1.0...iree-3.2.0rc20250206(Contributors can edit this section as they land patches)
Notable changes
Framework support
.tflite
to.mlirbc
may not be compatible with the IREE compiler. See Bump to llvm/llvm-project@3f1486f #19683 for more details.Compiler
legacy_sync
compilation mode has been removed since all in-tree compiler targets have been migrated off of it. The remaining asynchronous mode produces non-blocking operations that enable more multi-device parallelism.llvm-cpu
target now supports parsing AArch64 cpu features.Runtime
IREE_WHOLE_BUFFER
value was renamed toIREE_HAL_WHOLE_BUFFER
.Development tools
Full changelog
v3.1.0...v3.2.0
The text was updated successfully, but these errors were encountered: