Mark Elliot

Sorry for the delay, just gave that whirl, and docker produces the following stderr output: ``` ERROR: Multiple platforms feature is currently not supported for docker driver. Please switch to...

According to [the docs](https://docs.docker.com/build/buildkit/) BuildKit is default as of Docker 23.0 and I'm Docker 24.0, so I think this has no effect.

aha, magic. Thanks. I had to drop the final `container` in the first command to get things to run but that did the trick. Weirdly I'm having to plumb through...

It seems to me like this level of setup shouldn't be required/I'll have to figure out how to engineer the same set of state onto my CI system vs. just...

How about landing a symlink back to any .tool-versions file that was ever used by rtx and gc can check whether the file still exists, and if it does, then...

Not quite, -U allows all requirements in the output to be updated but -P specifically operates with the new constraint _and_ updates only the minimal set of requirements in the...

Yep, so expectation of -P foo==1.2.3 is: - apply an additional constraint of “foo==1.2.3” - allow only output requirements necessary to meet this constraint to upgrade - still meet all...

Good call -- can also confirm I'm seeing this for `oci_pull` defined repos in MODULE.bazel.

Here's a minimal repro on Bazel 7.1.1: https://github.com/mark-thm/td-81 Running `target-determinator HEAD~1` with t-d 0.26.0 produces no changed targets -- the hash for the image base was changed, though.

Running `bazel cquery 'deps(//:test)'` seems to produce different results between the commits: 5101a964cf6257720ac70242d03349b328d7585d (first commit) ``` //:test (7170974) @ubuntu//:ubuntu (7170974) @bazel_tools//tools/sh:toolchain_type (7170974) @rules_oci//oci/private:image.sh (null) @@aspect_bazel_lib~//lib:jq_toolchain_type (7170974) @@bazel_tools~sh_configure_extension~local_config_sh//:local_sh (7170974) @@rules_oci~~oci~oci_crane_darwin_arm64//:crane_toolchain (7170974)...