Repository navigation
fix(config): preserve native literal build paths - #188
Merged
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
added 8 commits
October 8, 2026 01:24
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Native builds whose context contains literal dollar expressions can fail when Compose translates the path into Bake expressions. The supported context/Dockerfile/target subset now uses direct Buildx arguments under the existing generation owner, preserving path bytes and producing exact owned image tags. Compose consumes those images without rebuilding.
The owner rechecks source, image identity, cancellation and deadlines around build effects. Omitted build policy reuses a qualified image; explicit rebuild changes it. Cold one-off commands build their target and dependencies; saved routed one-off commands preserve running dependencies and routes. Failures retain pending recovery state. Advanced build options, secrets and SSH are refused before hooks or engine effects.
Validation at
9799f4a6:Ordinary BuildKit cache remains retained. This change does not claim cache reclamation, advanced-option parity or a measured performance improvement.