61592f039d
fix license in build.zig.zon
AWS-Zig Build / build-zig-amd64-host (push) Successful in 2m56s
aws-zig nightly build / build-zig-nightly (push) Failing after 2m54s
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Successful in 3m41s
2024-06-08 10:17:40 -07:00
7d80f42a3e
update to zig 0.13-dev.365 (zig nominated build 2024.05)
aws-zig mach nominated build / build-zig-nominated-mach-latest (push) Failing after 1m57s
aws-zig nightly build / build-zig-nightly (push) Failing after 3m49s
2024-06-04 14:53:09 -07:00
c40539b7b0
remove "zig" from package name
AWS-Zig Build / build-zig-amd64-host (push) Successful in 3m13s
2024-05-15 13:19:46 -07:00
484b504090
add paths to build.zig.zon
AWS-Zig Build / build-zig-0.11.0-amd64-host (push) Failing after 2m33s
2024-04-22 09:17:10 -07:00
57e994f80f
upgrade to working smithy
2024-04-02 11:04:40 -07:00
d46cb9c28b
update smithy
aws-zig mach nominated build / build-zig-nightly (push) Failing after 1m11s
aws-zig nightly build / build-zig-nightly (push) Failing after 1m1s
2024-04-02 10:26:33 -07:00
d442671275
upgrade zig build gen build command to zig 0.12
...
This removes the copied Package.zig as we can now use the actual package
manager and look at our available dependencies in build.zig. This may
break again later as I believe lazy dependencies are planned, which will
have us search for a solution to tell the build system we're expecting
this dependency.
2024-03-30 15:26:24 -07:00
79d73cf09f
support for enum, document, and...dear lord...unit
2024-02-29 13:53:32 -08:00
8760662cf7
partial upgrade of build
2023-08-04 16:40:24 -07:00
