Zig 0.12.0 upgrade tracking issue #1

New Issue

lobo · 2024-05-01T14:28:56Z

lobo commented

2024-05-01 14:28:56 +00:00

There are a couple of one-time 0.11.0 -> 0.12.0 specific upgrade tasks:

make lambda-zig a direct dependency #2
make cloudflare-worker-deploy a direct dependency #3

There are a number of dependencies to upgrade to the next version of zig:

flexilib: completed as of c06bda918b
lambda-zig: completed as of cd9bf618f1
- aws-sdk-zig (should be a dependency, but is not)
cloudflare-worker-deploy: completed as of 00e0c51ac0

There are a couple of one-time 0.11.0 -> 0.12.0 specific upgrade tasks: - [x] make lambda-zig a direct dependency #2 - [x] make cloudflare-worker-deploy a direct dependency #3 There are a number of dependencies to upgrade to the next version of zig: - [x] [flexilib](https://git.lerch.org/lobo/FlexiLib): completed as of [c06bda918b](https://git.lerch.org/lobo/FlexiLib/commit/c06bda918b893ea1036cbd73136e04929a7c5667) - [x] [lambda-zig](https://git.lerch.org/lobo/lambda-zig/): completed as of [cd9bf618f1](https://git.lerch.org/lobo/lambda-zig/src/commit/cd9bf618f193bc96829c6edc90886ca9bb084fe0) - [x] aws-sdk-zig (should be a dependency, but is not) - [x] [cloudflare-worker-deploy](https://git.lerch.org/lobo/cloudflare-worker-deploy): completed as of [00e0c51ac0](https://git.lerch.org/lobo/cloudflare-worker-deploy/commit/00e0c51ac0b3f10c5ab215002b9fe44d7a1d281f)

lobo pinned this 2024-05-01 14:29:56 +00:00

lobo commented

2024-05-10 20:59:48 +00:00

completed via several commits, the last of which was c77502d addressing CI

completed via several commits, the last of which was c77502d addressing CI

lobo closed this issue

2024-05-10 20:59:51 +00:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lobo/universal-lambda-zig#1