Consider add a new release?

[tw4452852]

As we already transitioned to the new hash format, but the latest 1.3.1 tag still points to the old one.

[giodueck]

I'm also butting up against this. If I'm online, no problem as Zig will just fetch upstream zlib (as it does not match the hash), annoying, but it builds. If I'm not, the build will fail even if it should be the same thing as a minute ago. I bumped into this because of a slightly spotty Wifi connection.

As a (pretty ugly) workaround, manually modifying ~/.cache/zig/p/zlib-1.3.1-AAAAACEMAAA0qyoSrfgBb_p25ItL4yRf_TBRk-26TYMF/build.zig.zon to set the hash to this fixes it:

        .zlib = .{
            .url = "https://github.com/madler/zlib/archive/refs/tags/v1.3.1.tar.gz",
            .hash = "N-V-__8AADO1PwB9NTYJ2VzunaeJGRnm2Vgul7eqKDG9UPM7",
        },

[giodueck]

After a little experimentation with the package manager, the proper workaround is to instead target a commit instead of a release, for example with zig fetch --save http://github.com/allyourcodebase/zlib/archive/8a8161babd4b79ea47d5a5976337a96ac4a5666b.tar.gz

[xaviershay]

Came here to request a release also 🙏

[zigeth]

Came here to request a release also 🙏

pro tip: Compression algorithms. gzip and zlib are here: std.compress.flate