Skip to content

Update ZIG_VERSION in .devcontainer/Dockerfile#2125

Open
hulto wants to merge 1 commit intomainfrom
update-zig-version-8691905823095578159
Open

Update ZIG_VERSION in .devcontainer/Dockerfile#2125
hulto wants to merge 1 commit intomainfrom
update-zig-version-8691905823095578159

Conversation

@hulto
Copy link
Collaborator

@hulto hulto commented Mar 22, 2026

This change updates the ZIG_VERSION argument in .devcontainer/Dockerfile from 0.16.0-dev.2877+627f03af9 to the latest master version 0.16.0-dev.2962+08416b44f. This update is necessary to resolve potential Docker build CI failures caused by the unavailability of older development versions on Zig's servers. All relevant Go and Rust tests have been run and passed, ensuring that the environment update does not introduce regressions.


PR created automatically by Jules for task 8691905823095578159 started by @hulto

Following a Docker build CI failure on the main branch, this commit updates the
ZIG_VERSION in .devcontainer/Dockerfile to the latest master version available.
This ensures that the build process uses a current toolchain, avoiding issues
where older development binaries are no longer available on Zig's servers.

Verified by checking the latest version at https://ziglang.org/download/index.json
and running existing tests to ensure environment stability.

Co-authored-by: hulto <7121375+hulto@users.noreply.github.com>
@google-labs-jules
Copy link
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions
Copy link
Contributor

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
2833    ±0 2833    ±0 0    ±0 0    ±0 0    ±0 0    ±0 1ms    ±0

Previous Results

Build 🏗️ Result 🧪 Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
#1826 2833 2833 0 0 0 0 39.8s

Insights

Average Tests per Run Total Flaky Tests Total Failed Slowest Test (p95)
2833 0 0 5.6s

Test Changes

0 test added, 0 removed

Slowest Tests

Test 📝 Results 📊 Duration (avg) ⏱️ Duration (p95) ⏱️
TestDockerExecutor_Build_ContextCancellation 1 5.6s 5.6s
eldritch-libsys: std::dll_inject_impl::tests::test_dll_inject_simple 1 5.1s 5.1s
TestInteractiveShell 1 5.0s 5.0s
TestOtherStreamOutput 1 5.0s 5.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_streaming_error 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s
imix::bin/imix: tests::task_tests::test_task_eprint_behavior 3 3.0s 3.0s

🎉 No failed tests in this run. | 🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant