Skip to content

chore: update package hashes - #49

Draft
neoto wants to merge 1 commit into
allyourcodebase:mainfrom
neoto:package-hash
Draft

neoto wants to merge 1 commit into
allyourcodebase:mainfrom
neoto:package-hash

Conversation

@neoto

@neoto neoto commented Oct 22, 2026

Copy link
Copy Markdown

Helps with building for the latest Zig after this PR got merged.

Creating this as a draft because I have no idea if we want to specify anything under paths, and if so, what exactly.

@neoto

neoto commented Oct 22, 2026

Copy link
Copy Markdown
Author

Uhhh, so, I guess I should have added that this breaks everything prior to that commit because of obvious reasons. Not sure what the policy is in this case

@jayschwa

Copy link
Copy Markdown
Collaborator

All Your Codebase projects must work with the latest released version of Zig. Support for master builds is nice to have, but can't break support for the latest release. If building with 0.18.0-dev absolutely requires breaking support for 0.17.x, then I suppose we could start a branch for the former.

@neoto

neoto commented Oct 22, 2026

Copy link
Copy Markdown
Author

Gotcha. I'll let you do what you think makes sense. I can always use my fork or local package instead.

@jayschwa

Copy link
Copy Markdown
Collaborator

I will test the naked package metadata changes once the ziglang.org master tarballs update. I have an idea for a workaround to keep it working for both 0.17.0 and 0.18.0-dev.

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