-
Notifications
You must be signed in to change notification settings - Fork 260
fix: Re-enable codespaces #4124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes codespace configuration issues by explicitly pinning the development container to Debian bullseye. The change updates the Docker image variant from "1.24" to "1.24-bullseye" to ensure compatibility with codespace utilities that have dependencies on this Debian distribution.
Key Changes:
- Explicitly specify Debian bullseye distribution in devcontainer VARIANT to fix codespace compatibility
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/azp run Azure Container Networking PR |
|
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
* test: 1.24.1 * test: bullseye * test: trixie | 6.12 * test: revert devcontainers/features/go version * test: revert trixie, no build * ci: bump devcontainer go features to 1.24.1
Reason for Change:
Our codespace utils have dependencies on bullseye. Going to pin to bullseye until we update to GO 1.25, which we then should update to trixie
This has been broken since #3912.
Bullseye
Trixie
Issue Fixed:
Requirements:
Notes:
Go 1.25.1 has been released for some time now. https://go.dev/doc/go1.25