also looking at this
fix(ci): build the SDK types with the repo's own tsc (and pin the pantry action)
#104
29 files
+85
-56
| @@ -5,6 +5,13 @@ dependencies: | ||
| 5 | 5 | bun.sh: 1.3.14 |
| 6 | 6 | # Also pinned exactly. `^0.17.0-dev` floats on Zig's *dev* channel, so any |
| 7 | 7 | # `pantry install` can swap the compiler out from under a build — observed |
| 8 | # jumping 1509 -> 1606 unprompted. This is the version v0.0.58 was released | |
| 9 | # with. Bump deliberately, and rebuild when you do. | |
| 10 | ziglang.org: 0.17.0-dev.1509_bb296ab9b | |
| 8 | # jumping 1509 -> 1606 unprompted. Bump deliberately, and rebuild when you do. | |
| 9 | # | |
| 10 | # The pin has a shelf life, which 1509 is how we found out. ziglang.org | |
| 11 | # serves exactly one dev build — whatever master is now — plus the tagged | |
| 12 | # releases, and prunes the rest. Every platform tarball for 1509 returned | |
| 13 | # 404, so CI was running on cached toolchains and any uncached runner failed | |
| 14 | # to provision at all: `darwin-x64` went red on a lockfile-free PR, and the | |
| 15 | # next tagged release would have failed the same way. A pinned dev build is | |
| 16 | # reproducible only for as long as it is master. | |
| 17 | ziglang.org: 0.17.0-dev.1963_e00c6c439 | |