Skip to content

Conversation

isaacvando
Copy link
Collaborator

@isaacvando isaacvando commented Sep 7, 2025

My default approach has been to make the smallest possible changes to keep the risk of introducing bugs low. Then we can come back around later and fully migrate to the new APIs with a fully working build and an easier time testing. For example, I've chosen to use .deprecatedWriter() whenever possible here rather than migrating to the new std.io.Writer interface everywhere in one go.

I haven't landed in a good spot yet with bundle/unbundle, so if someone else takes a look at this, you might want to forget about those commits and start fresh. The chains of readers and writers make things more difficult, and some old APIs have been completely changed/removed rather than deprecated like the old buffered writer and the old tar writer.

@isaacvando isaacvando force-pushed the upgrade-to-zig-0.15.1 branch 2 times, most recently from abf5810 to 208a6ac Compare September 9, 2025 03:36
@isaacvando isaacvando force-pushed the upgrade-to-zig-0.15.1 branch from 208a6ac to a0f05d0 Compare September 9, 2025 23:38
@Anton-4 Anton-4 self-assigned this Sep 22, 2025
@Anton-4
Copy link
Collaborator

Anton-4 commented Sep 22, 2025

  • Search for references to ".14"
  • Revert all changes to crates folder

@Anton-4
Copy link
Collaborator

Anton-4 commented Sep 26, 2025

Currently stuck on:

❯ zig build test
test
└─ run test bundle_test 26/27 passed, 1 failed
General protection exception (no address available)

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.

3 participants