Skip to content

Revert "Add git-tree-{sha1,sha256} (but only for .tar.gz downloads)"#79

Closed
DilumAluthge wants to merge 2 commits into
mainfrom
revert-64-codex/tarball-git-tree-sha1
Closed

Revert "Add git-tree-{sha1,sha256} (but only for .tar.gz downloads)"#79
DilumAluthge wants to merge 2 commits into
mainfrom
revert-64-codex/tarball-git-tree-sha1

Conversation

@DilumAluthge
Copy link
Copy Markdown
Member

Reverts #64

This is only a temporary revert. Computing treehashes takes a long time, and now our build times are hitting GitHub's 6 hour time limit. So let's revert for now.

Once #67 has been merged, I'll reland this, because build times should be much better at that point.

@DilumAluthge DilumAluthge requested a review from ararslan April 28, 2026 21:38
@DilumAluthge
Copy link
Copy Markdown
Member Author

DilumAluthge commented Apr 28, 2026

test-current-s3 is expected to fail with this PR, and it will pass again once we re-deploy.

@DilumAluthge
Copy link
Copy Markdown
Member Author

I went ahead and fixed the test-current-s3 test now. I just kept the git-tree-sha{1,256} keys as allowed but optional.

@DilumAluthge DilumAluthge added this pull request to the merge queue Apr 28, 2026
Copy link
Copy Markdown
Member

@ararslan ararslan left a comment

Choose a reason for hiding this comment

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

Looks good to me, though I'm not familiar enough with JSON schemas to know what effect removing the fields from schema.json will have, if any.

@DilumAluthge DilumAluthge removed this pull request from the merge queue due to a manual request Apr 28, 2026
@DilumAluthge
Copy link
Copy Markdown
Member Author

DilumAluthge commented Apr 28, 2026

Ah, you're right. I should keep it in the schema, albeit as an optional field.

@DilumAluthge
Copy link
Copy Markdown
Member Author

Closing in favor of #81 (which is narrower than this PR, but still accomplishes the main goal).

@DilumAluthge DilumAluthge deleted the revert-64-codex/tarball-git-tree-sha1 branch May 2, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants