update CI/CD

.gitea/workflows/build.yaml

@@ -2,14 +2,14 @@ name: AWS-Zig Build
 run-name: ${{ github.actor }} building AWS Zig SDK
 on: [push]
 jobs:
-  build-zig-0.9-amd64-host:
+  build-zig-0.11.0-amd64-host:
     runs-on: ubuntu-latest
     # Need to use the default container with node and all that, so we can
     # use JS-based actions like actions/checkout@v3...
     # container:
     #   image: alpine:3.15.0
     env:
-      ZIG_VERSION: 0.9.0
+      ZIG_VERSION: 0.11.0
       ARCH: x86_64
     steps:
       - name: Check out repository code
@@ -24,7 +24,6 @@ jobs:
       - run: ln -s /usr/local/zig-linux-${ARCH}-${ZIG_VERSION}/zig /usr/local/bin/zig
       - run: apt update && apt install --no-install-recommends git
       - run: (cd codegen && zig build test)
-      - run: zig build -Dfetch # implicitly does a codegen
       - run: zig build test
       - run: zig build -Dtarget=arm-linux
       - run: zig build -Dtarget=x86_64-windows
@@ -33,7 +32,7 @@ jobs:
       - run: zig build -Dtarget=x86_64-macos
       - run: zig build -Dtarget=aarch64-macos
       - name: Notify
-        uses: https://git.lerch.org/lobo/action-notify-ntfy@v1
+        uses: https://git.lerch.org/lobo/action-notify-ntfy@v2
         if: always()
         with:
           host: ${{ secrets.NTFY_HOST }}

src/main.zig

@@ -202,6 +202,9 @@ pub fn main() anyerror!void {
                     const more = try aws.Request(services.ec2.describe_instances)
                         .call(.{ .next_token = next_token, .max_results = 6 }, options);
                     defer more.deinit();
+                    // we could have exactly 6, which means we have a next token(?!) but not
+                    // any actual additional data
+                    if (more.response.reservations == null) break;
                     std.log.info("reservation count: {d}", .{more.response.reservations.?.len});
                     var batch_items: usize = 0;
                     for (more.response.reservations.?) |reservation| {