Skip to content

Conversation

@charlielye
Copy link
Contributor

@charlielye charlielye commented Dec 27, 2025

aztec-up can be used to manage multiple versions.

$ aztec-up
aztec-up - Aztec version manager

Usage: aztec-up [command] [options]

Commands:
  install <version>         Install a version and switch to it
  use [<version>]           Switch to an installed version (or read from .aztecrc)
  list                      List installed versions
  uninstall <version>       Remove an installed version
  self-update               Update aztec-up itself to the latest version

Options:
  -h, --help                Show this help message

Examples:
  aztec-up install          Install the latest version
  aztec-up install nightly  Install the latest nightly version
  aztec-up install 0.85.0   Install a specific version
  aztec-up use 0.85.0       Switch to version 0.85.0
  aztec-up use              Read version from .aztecrc and switch to it
  aztec-up list             Show all installed versions
  aztec-up self-update      Update aztec-up to latest

If a .aztecrc file is present in the cwd, aztec will automatically switch to that version in that run context.

t % aztec --version
0.0.1-commit.1142ef1
t % cd fooproj
t % cat .aztecrc
0.0.1-commit.6d3c34e
t % aztec --version
0.0.1-commit.6d3c34e
t %

Testing

You can install aztec-up with:

VERSION=0.0.1-commit.6d3c34e bash -i <(curl -s https://install.aztec.network/0.0.1-commit.6d3c34e/aztec-install)

At present you can't list available remote versions. The code does currently support listing available remote aliases, but they're not deployed yet. You can install another version with e.g.

aztec-up install 0.0.1-commit.1142ef1

Then list versions with:

t % aztec-up list
Installed versions:

* 0.0.1-commit.1142ef1 (current)
  0.0.1-commit.6d3c34e

Aliases:
  (could not fetch aliases)

Copy link
Contributor Author

charlielye commented Dec 27, 2025

@charlielye charlielye changed the title inital feat: aztec-up can be used to manage multiple aztec versions Dec 27, 2025
@charlielye charlielye marked this pull request as ready for review December 27, 2025 13:35
@olehmisar
Copy link
Contributor

a suggestion:

does this make aztec command read from .aztecrc as well?

E.g., the ideal workflow (similar to gaztec):

bash -i <(curl -s https://install.aztec.network)
aztec --version
#> 2.1.9 # the latest version by default

echo 3.0.0 > .aztecrc
aztec --version
#> 3.0.0

# in another project
echo 3.0.0-devnet.5 > .aztecrc
aztec --version
#> 3.0.0-devnet.5

Note that aztec-up was never used. Calling aztec should automatically install the version from .aztecrc or fallback to the global installed version (when aztec-up was last called).

This mimics how rust-toolchain.toml works. Maybe worth using aztec-toolchain.toml instead of .aztecrc to make it extendable in the future?

@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from ec9d893 to d28e3da Compare January 6, 2026 11:07
@charlielye charlielye force-pushed the cl/install_dockerless branch from 37c2b1a to 13a3485 Compare January 6, 2026 11:07
@charlielye charlielye requested a review from alejoamiras January 6, 2026 16:06
@charlielye charlielye force-pushed the cl/install_dockerless branch from b94f1ff to d10ef23 Compare January 7, 2026 18:48
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from 17ad593 to ad42667 Compare January 7, 2026 18:48
@charlielye charlielye force-pushed the cl/install_dockerless branch from d10ef23 to d6c115a Compare January 8, 2026 10:46
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from a35138c to 110f422 Compare January 8, 2026 10:46
@charlielye charlielye force-pushed the cl/install_dockerless branch from d6c115a to d213ad3 Compare January 8, 2026 10:50
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch 2 times, most recently from 4996807 to 0556d70 Compare January 8, 2026 12:16
@charlielye charlielye force-pushed the cl/install_dockerless branch from 163b2aa to 8e792d8 Compare January 9, 2026 12:44
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from 0556d70 to 3075d4a Compare January 9, 2026 12:44
@charlielye charlielye force-pushed the cl/install_dockerless branch from 8e792d8 to ab988be Compare January 9, 2026 14:44
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from 3075d4a to f92cdcb Compare January 9, 2026 14:44
@charlielye charlielye force-pushed the cl/install_dockerless branch from beef6e1 to a85f821 Compare January 9, 2026 19:19
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch 2 times, most recently from 62c24b9 to 0451dec Compare January 9, 2026 20:08
@charlielye charlielye force-pushed the cl/install_dockerless branch from a85f821 to 530d114 Compare January 9, 2026 20:08
@AztecBot
Copy link
Collaborator

AztecBot commented Jan 12, 2026

Flakey Tests

🤖 says: This CI run detected 4 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/493222b4f726cd6f�493222b4f726cd6f8;;�): yarn-project/end-to-end/scripts/run_test.sh web3signer src/composed/web3signer/e2e_multi_validator_node_key_store.test.ts (39s) (code: 1) (\033Charlie\033: feat: aztec-up can be used to manage multiple aztec versions (#19261))
\033FLAKED\033 (8;;http://ci.aztec-labs.com/2d7829156b14579f�2d7829156b14579f8;;�): yarn-project/scripts/run_test.sh prover-client/src/proving_broker/proving_broker.test.ts (33s) (code: 1) (\033Charlie\033: feat: aztec-up can be used to manage multiple aztec versions (#19261))
\033FLAKED\033 (8;;http://ci.aztec-labs.com/4c08f47b02c2fb7b�4c08f47b02c2fb7b8;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_high_tps_block_building.test.ts (290s) (code: 1) group:e2e-p2p-epoch-flakes (\033Charlie\033: feat: aztec-up can be used to manage multiple aztec versions (#19261))
\033FLAKED\033 (8;;http://ci.aztec-labs.com/09dca57bcbcf24f5�09dca57bcbcf24f58;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_invalidate_block.parallel.test.ts "proposer invalidates multiple blocks" (602s) (code: 124) group:e2e-p2p-epoch-flakes (\033Charlie\033: feat: aztec-up can be used to manage multiple aztec versions (#19261))

@AztecBot AztecBot force-pushed the cl/install_dockerless branch from cd2bf56 to 0ffc1e0 Compare January 12, 2026 14:49
Base automatically changed from cl/install_dockerless to next January 12, 2026 16:15
@charlielye charlielye force-pushed the cl/aztec-up_version_manager branch from b94556e to 7a9085a Compare January 12, 2026 16:22
@auth.verify_password
def verify_password(username, password):
if username == "aztec" and password == "letmeseethoselogs":
if username == "aztec" and password == DASHBOARD_PASSWORD:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

luckily there's probably no overlap between github farmers and API-probing bots

case $cmd in
test)
export LOG_LEVEL="${LOG_LEVEL:-info}"
export LOG_LEVEL="${LOG_LEVEL:-error}"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm not having LOG_LEVEL=info is clean but I wonder if it will make it harder when people report their issues

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unless I'm missing something, I thought the TXE should basically be operating transparently. It's obviously useful to see error messages, but INFO is basically debug in this context right? It's nargo that's giving all the useful feedback? Trivial to revert later if needed.

# This script is called by aztec-up to install a specific version of the Aztec toolchain.
# It expects VERSION and INSTALL_URI to be set.
set -euo pipefail
shopt -s inherit_errexit
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: At first guess I would say 0.0.1/install is not the current source

@AztecBot AztecBot force-pushed the cl/aztec-up_version_manager branch from 7d4e6cd to d041e39 Compare January 14, 2026 09:59
@AztecBot AztecBot enabled auto-merge January 14, 2026 09:59
@AztecBot AztecBot force-pushed the cl/aztec-up_version_manager branch from d041e39 to c7e2941 Compare January 14, 2026 10:02
@AztecBot AztecBot added this pull request to the merge queue Jan 14, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 14, 2026
@charlielye charlielye added this pull request to the merge queue Jan 14, 2026
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 14, 2026
@charlielye charlielye enabled auto-merge January 14, 2026 22:27
@AztecBot AztecBot force-pushed the cl/aztec-up_version_manager branch from f942892 to a349f20 Compare January 14, 2026 22:54
`aztec-up` can be used to manage multiple versions.

```
$ aztec-up
aztec-up - Aztec version manager

Usage: aztec-up [command] [options]

Commands:
  install <version>         Install a version and switch to it
  use [<version>]           Switch to an installed version (or read from .aztecrc)
  list                      List installed versions
  uninstall <version>       Remove an installed version
  self-update               Update aztec-up itself to the latest version

Options:
  -h, --help                Show this help message

Examples:
  aztec-up install          Install the latest version
  aztec-up install nightly  Install the latest nightly version
  aztec-up install 0.85.0   Install a specific version
  aztec-up use 0.85.0       Switch to version 0.85.0
  aztec-up use              Read version from .aztecrc and switch to it
  aztec-up list             Show all installed versions
  aztec-up self-update      Update aztec-up to latest
```

If a `.aztecrc` file is present in the cwd, `aztec` will automatically switch to that version in that run context.

```
t % aztec --version
0.0.1-commit.1142ef1
t % cd fooproj
t % cat .aztecrc
0.0.1-commit.6d3c34e
t % aztec --version
0.0.1-commit.6d3c34e
t %
```

# Testing

You can install `aztec-up` with:
```
VERSION=0.0.1-commit.6d3c34e bash -i <(curl -s https://install.aztec.network/0.0.1-commit.6d3c34e/aztec-install)
```

At present you can't list available remote versions. The code does currently support listing available remote aliases, but they're not deployed yet. You can install another version with e.g.
```
aztec-up install 0.0.1-commit.1142ef1
```

Then list versions with:

```
t % aztec-up list
Installed versions:

* 0.0.1-commit.1142ef1 (current)
  0.0.1-commit.6d3c34e

Aliases:
  (could not fetch aliases)
```
@AztecBot AztecBot force-pushed the cl/aztec-up_version_manager branch from a349f20 to f69c7bf Compare January 14, 2026 22:57
@charlielye charlielye added this pull request to the merge queue Jan 14, 2026
Merged via the queue into next with commit 392563c Jan 14, 2026
17 checks passed
@charlielye charlielye deleted the cl/aztec-up_version_manager branch January 14, 2026 23:35
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.

5 participants