Skip to content

Conversation

@abderrahim
Copy link
Contributor

@abderrahim abderrahim commented Jan 29, 2026

Before this change, running a build with --deps none would also build / pull runtime dependencies. This commit changes the elements on the command line to not require their runtime dependencies if we're using --deps none.

In addition to the config file option dependencies none and all, this PR adds run and makes it the
default instead of none. The previous commit changed the meaning of
--deps none to be different from --deps run, so we change the default to be
run.

Before this change, running a build with `--deps none` would also build / pull
runtime dependencies. This commit changes the elements on the command line to
not require their runtime dependencies if we're using `--deps none`
In addition to `none` and `all`, this commit adds `run` and makes it the
default instead of `none`. The previous commit changed the meaning of
`--deps none` to be different from `--deps run`, so we change the default to be
`run`.
@juergbi
Copy link
Contributor

juergbi commented Jan 30, 2026

The proposed behavior seems reasonable. Looking at the documentation, the current none behavior might not have been intentional. It is technically still a breaking change from the CLI/config perspective but it may be acceptable for 2.7 given the default user config update which mitigates the change (and it won't break project config or element definitions).

I'd like to see at least minimal test coverage, though (could be a current test that is slightly expanded).

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.

2 participants