Delete old releases #21
Open
Conversation
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
…CI build fix is valid." This reverts commit 1bc10af.
|
Hi @marbre, @stellaraccident, @saienduri, @sjain-stanford can you take a look please? Don't have write permissions in this repo, so just tagging you all. Thanks! |
I was made aware of this issue during the LLVM dev mtg but didn't had a chance to yank old releases as I was still traveling. Hoping to find a bit more time soon. |
|
As another user/stakeholder of the python packages -- thank you, @sahas3! Upon discussion with @marbre and @banach-space, we also figured the 1000 files limit is the current issue. The changes you propose seem right on the money to me 👍 |
banach-space
approved these changes
Nov 5, 2025
banach-space
approved these changes
Nov 5, 2025
sahas3
force-pushed
the
deleteOldReleases
branch
from
51890ea to
5d1fa67
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Releasing the wheels has been failing for a month now https://github.com/llvm/torch-mlir-release/actions/runs/19032410905/job/54349329471#step:7:30 due to the GH limit that each release artifact can only have a maximum of 1000 artifacts (some discussion captured here https://github.com/orgs/community/discussions/165616).
This PR has two changes:
An alternative to keeping all the assets will probably be to release the assets with new name daily but seems overkill to me. Open to other suggestions as well.
artifactErrorsFailBuildflag on the release CIs which I think will cause the builds to fail if the upload step fails -- currently the build doesn't fail which is why I think we didn't notice this earlier.