You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
0.13.0 is a major release, with several enhancements to improve the Python development experience with Devbox.
[Python] Autopatching Native Libraries
This release includes an experimental feature that automatically patches Python interpreters to load native libraries installed in your Devbox Shell, without needing to set LD_LIBRARY_PATH. This makes it easier to create Devbox shells for projects with Python Packages that use native extensions. Additionally, Devbox will automatically install native libraries that are commonly used by Python packages, such as zlib and openssl. This feature can be disabled with devbox add <python-package> --patch never
This release automatically enables patching for Python interepreters, but it can be enabled for any package (such as Ruby) using devbox add <pkg> --patch always.
When you launch Python, our plugin now defaults to putting your virtual environment in $DEVBOX_PROJECT_ROOT/.venv. This provides better compatibility with IDEs and Language Extensions that expect Python to be in your project root. The plugin also sets a UV_PYTHON environment variable to improve compatibility with the uv package manager.
You can manage where Devbox sets up your .venv directory by setting the $VENV_DIR environment variable in your devbox.json.
Special thanks to @djgoku for contributing fixes to this feature!
[Services] devbox services attach and better backgrounding
Starting Devbox services in the background with devbox services up -b now runs process-compose as a detached process in the background, meaning it will stay alive even if your terminal exits or crashes. You can attach the process-compose TUI to the backgrounded process with devbox services attach, and exiting the TUI will leave process-compose running in the background.
To stop the backgrounded process, you can use devbox services stop.
This release also upgrades the default process-compose to 1.24.2, which has several reliability and performance improvements.
Other Features
Devbox can now automatically parse and add secrets from your dotenv files. To have Devbox load your dotenv files automatically, add the dotenv file to env_from in your devbox.json
Devbox now includes a builtin plugins for Valkey, a drop-in Redis Replacement. Special thanks to @captainseeker for contributing!
Added a DEVBOX_WD environment variable that maps to the working directory where you ran a script. This variable is useful if you want to run scripts that act on your current working directory, instead of the Devbox project's root directory
Devbox's direnv integration now watched devbox.lock for changes, and updates your environment. Thanks to @mjgallag for contributing!
Added missing/required properties to the devbox-plugin-schema.json. Thanks to @svallory for contributing!
Full Changelog
[docs] json format fix of configuration.md by @yocoldle in #2168
Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.
Affected range
>=1.23.0-0 <1.23.1
Fixed version
1.23.1
Description
Calling any of the Parse functions on Go source code which contains deeply nested literals can cause a panic due to stack exhaustion.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.12.0->0.13.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
jetify-com/devbox (jetify-com/devbox)
v0.13.0Compare Source
What's new in this release
0.13.0 is a major release, with several enhancements to improve the Python development experience with Devbox.
[Python] Autopatching Native Libraries
This release includes an experimental feature that automatically patches Python interpreters to load native libraries installed in your Devbox Shell, without needing to set
LD_LIBRARY_PATH. This makes it easier to create Devbox shells for projects with Python Packages that use native extensions. Additionally, Devbox will automatically install native libraries that are commonly used by Python packages, such aszlibandopenssl. This feature can be disabled withdevbox add <python-package> --patch neverThis release automatically enables patching for Python interepreters, but it can be enabled for any package (such as Ruby) using
devbox add <pkg> --patch always.[Python] Plugin + Virtual Environment improvements
When you launch Python, our plugin now defaults to putting your virtual environment in $DEVBOX_PROJECT_ROOT/.venv. This provides better compatibility with IDEs and Language Extensions that expect Python to be in your project root. The plugin also sets a
UV_PYTHONenvironment variable to improve compatibility with theuvpackage manager.You can manage where Devbox sets up your .venv directory by setting the $VENV_DIR environment variable in your devbox.json.
Special thanks to @djgoku for contributing fixes to this feature!
[Services]
devbox services attachand better backgroundingStarting Devbox services in the background with
devbox services up -bnow runs process-compose as a detached process in the background, meaning it will stay alive even if your terminal exits or crashes. You can attach the process-compose TUI to the backgrounded process withdevbox services attach, and exiting the TUI will leave process-compose running in the background.To stop the backgrounded process, you can use
devbox services stop.This release also upgrades the default process-compose to 1.24.2, which has several reliability and performance improvements.
Other Features
env_fromin your devbox.jsonDEVBOX_WDenvironment variable that maps to the working directory where you ran a script. This variable is useful if you want to run scripts that act on your current working directory, instead of the Devbox project's root directoryFull Changelog
devbox.Findby @gcurtis in #2172lookPathhelper to find nix binaries by @gcurtis in #2247.venvscript to be more compatible with IDEs by @Lagoja in #2259attachcommand by @Lagoja in #2269New Contributors
Full Changelog: jetify-com/devbox@0.12.0...0.13.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.