Releases · jetify-com/devbox

08 Apr 20:54

github-actions

0.10.4-dev

653e884

0.10.4-dev Pre-release

Pre-release

0.10.4 Pre-release

Bug fixes for Jetpack Secrets and auth redirects
Fix for generated Dockerfiles
Adds a Bun example and template

Changelog

8e737d9 [docs] Added gopath example in docs (#1957)
33815df Bun Example and Template (#1913)
4df5a62 [caching] Add some basic AWS credentials caching (#1955)
53c8fff [gen-dockerfile] Make /code directory creation idempotent (#1956)
9aac11a [pat]Exchange pat for access token (#1947)
4253632 Bump webpack-dev-middleware from 5.3.3 to 5.3.4 in /docs/app (#1925)
7f70e1f Bump follow-redirects from 1.15.5 to 1.15.6 in /docs/app (#1906)
d93de56 Bump express from 4.18.2 to 4.19.2 in /docs/app (#1934)
eb4aa18 Bump rdoc from 6.6.2 to 6.6.3.1 in /examples/stacks/rails/blog (#1929)
47f2178 [auth] Change success redirect url (#1954)
514cddd Hotfix/doc readme link (#1952)
8563195 [gen-readme] For generated readme scripts, replace absolute paths (#1949)
46ea79e [secrets]Unbreak (#1950)

Assets 9

01 Apr 20:41

mikeland73

0.10.3

1ff72fa

0.10.3

What's Changed

This changes the oauth2 issuer domain from accounts.jetpack.io to accounts.jetify.com (For logged in use only. This has no effect on logged out use).

Full Changelog: 0.10.2...0.10.3

Assets 9

28 Mar 23:05

mikeland73

0.10.2

63981b0

0.10.2

This dot release includes the following fixes/features:

Fix bug where php and other packages with built in plugins could not be removed with devbox rm
Fix bug where some plugins were re-writing user files in devbox.d
Allow comments in plugin.json files. (similar to devbox.json). These comments are ignored when parsing.

What's Changed

0.10.0 Docs by @Lagoja in #1900
[Plugins] Do not overwrite existing user-config files of plugins by @savil in #1917
Support Project Directory having spaces by @savil in #1920
remove extraneous print by @savil in #1922
[plugins] support reading (and discarding) comments plugin.json files by @savil in #1923
[path with spaces] run scripts for projects with paths in spaces by @savil in #1924
Update nodejs README.md to include corepack by @LucilleH in #1928
[plugins] remove extraneous code change from #1917 by @savil in #1937
Revert "[path with spaces] run scripts for projects with paths in spaces (#1924)" by @savil in #1935
[docs] FAQ: add --experimental to nix store gc by @savil in #1941
[plugins] Fix rm for packages with __remove_trigger_package by @mikeland73 in #1940
[plugins] change pip venv shell hook recommendation to be posix-compatible by @savil in #1939

Full Changelog: 0.10.1...0.10.2

Contributors

mikeland73, savil, and 2 other contributors

Assets 9

15 Mar 20:34

github-actions

0.10.1

6758504

0.10.1

This release includes the following fixes for Devbox 0.10.0:

Fixes a bug that kept process-compose from updating on systems using Nix >2.20.
Corepack for Node.js is now an opt-in feature. Devs can enable corepack by setting DEVBOX_COREPACK_ENABLED in the env section of their devbox.json. For starting new projects, we recommend using Corepack to manage npm, yarn, or pnpm.

Changelog

6758504 [corepack] Make opt-in (#1905)
e0d0c06 [process-compose] Remove old process compose using store path (#1903)

Assets 9

15 Mar 00:25

github-actions

0.10.0

ff7b1cb

0.10.0 - Plugins v2, Non-default Outputs, Corepack support, and more

What's new in this Release

This new release includes a new, more powerful plugin system, support for installing non-default outputs in devbox.json without a Flake reference, and lots of other features.

You can update to the latest release by running devbox version update from your CLI. If you were testing a pre-release version of Devbox, you will need to unset DEVBOX_USE_VERSION before upgrading.

Plugins v2

This release includes an update to our Devbox Plugins to make them more flexible and powerful. These changes are backwards compatible, so your current plugins should work as expected.

Plugins now support all the fields from devbox.json, including scripts and packages:
- Specifying scripts in your plugin.json will make those scripts available in any project that imports your plugin
- Specifying packages in your plugin.json will install those packages in any project that imports your plugin
Plugins can now include/import other plugins in the include field
Plugins installed from a Github repo will now get their own directories in devbox.d and .devbox/virtenv, instead of being combined in a single folder. This makes it easier to host multiple plugins from a single repo.

This version also implements a merge algorithm that makes it possible to import multiple plugins, or even nest plugin imports. For more technical details, see the [#1850]

Alternate Outputs Support

You can now install alternate outputs for a package with devbox add using the --outputs flag, no flake references required.

For example, if you need to install the promtool cli along with the prometheus package, you can now run devbox add prometheus@latest --outputs=out,cli.

Corepack For NodeJS

Devbox now has a builtin plugin that configures Node.js packages to use Corepack. Corepack is a script bundled with Node.js that manages yarn, npm, and pnpm for your project without having to install them with Nix/Devbox. Huge thanks to @jasononeil and @jay-aye-see-kay for contributing the plugin.

We recommend using Corepack to install npm and other package managers instead of installing them directly with Devbox. Docs and examples will be updated to recommend Corepack

GLIBC Library Patching

This release updates Devbox's ability patch a package to use a newer version of glibc. This fix should help address version 'GLIBC_x.xx' not found errors that may occur when installing or running a mix of older and newer packages with Devbox, especially when using older versions of interpreted languages like Python or Ruby.

If you encounter this error in your project, you should run devbox add <package-name> --patch-glibc on the language interpreter or runtime. For example, if you encounter this with a Python 3.8 project, you should run devbox add [email protected] --patch-glibc.

This release also unsets the LD_LIBRARY_PATH and LIBRARY_PATH variables in Devbox Shell, which could cause compatibility or missing library issues.

This is an early, in development feature. Please let us know on Discord and Github if you run into any issues when patching glibc.

Process-compose 0.85.0

The version of process-compose used by Devbox has been updated to 0.85.0. We also refactored some code so that we can keep process-compose more up to date in the future
Additionally, we've updated Devbox to assign a random port to process-compose instead of using a pre-selected block, which should reduce the risk of port contention.

Other Fixes

Fixed a backwards compatibility issue with the last Devbox pre-release
Fixed a permissions issue on the /code directory when generating a Dockerfile. Thanks @agate for contributing this fix!
devbox update will now refresh git flakes to ensure that they are up to date. Thanks @kadaan for contributing this fix!
Fixed Github flake reference parsing to handle commit references + ?dir query parameters.
Fixed a bug where Devbox symlinks are not properly recognized on some systems.
Fixes a bug with parsing Flake URL references
Devbox environments will now update faster if you are adding a package that is already in your Nix store
devbox.json files created by the CLI now include our JSON schema
Removed recommendations when running devbox init, since these were not very relevant to users
Fixes to various examples and templates
Other small UX improvements and fixes