fix(aztec-up): pin FOUNDRY_DIR in foundry install to avoid XDG_CONFIG_HOME mismatch#22886
Merged
Merged
Conversation
vezenovm
approved these changes
Apr 30, 2026
AztecBot
pushed a commit
that referenced
this pull request
Apr 30, 2026
Collaborator
|
✅ Successfully backported to backport-to-v4-next-staging #22884. |
chrismarino
pushed a commit
to chrismarino/aztec-packages
that referenced
this pull request
May 5, 2026
BEGIN_COMMIT_OVERRIDE fix(aztec-up): run acceptance test after CI3 completes release (AztecProtocol#22850) feat(aztec-nr): assert contract function return types and params are serializable (AztecProtocol#22877) fix(aztec-up): pin FOUNDRY_DIR in foundry install to avoid XDG_CONFIG_HOME mismatch (AztecProtocol#22886) END_COMMIT_OVERRIDE
critesjosh
added a commit
that referenced
this pull request
May 18, 2026
Covers operator-facing changes in v4.3.0: - Bundled binaries renamed under aztec- prefix on PATH (#22902, #22709) - --pxe flag removed from aztec start (#22867) - aztec-up pins manifest Node version (#23201) - aztec-up pins FOUNDRY_DIR (#22886) Added to both source docs-operate/ and the v4.3.0 versioned snapshot, and linked from the operator changelog sidebar in both places.
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
3 participants
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.
Problem
The foundry installer (
foundry.paradigm.xyz) uses$XDG_CONFIG_HOME/.foundryas the install directory whenXDG_CONFIG_HOMEis set, instead of$HOME/.foundry. On CI runners whereXDG_CONFIG_HOMEis set,foundryupgets installed to an unexpected path (e.g./home/runner/.config/.foundry/bin/foundryup), causing the subsequentfoundryupinvocation to fail with "No such file or directory".Fix
Pin
FOUNDRY_DIR="$HOME/.foundry"on both sides of thecurl | bashpipe so we control wherefoundryupis installed regardless of the caller's environment.