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

Copy link
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@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
@AztecBot
Copy link
Collaborator

AztecBot commented Jan 6, 2026

Flakey Tests

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

\033FLAKED\033 (\0338;;http://ci.aztec-labs.com/4e7f351d7113ed3d�4e7f351d7113ed3d8;;�\033):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_p2p/add_rollup.test.ts (184s) (code: 1) group:e2e-p2p-epoch-flakes (\033Charlie\033: clean)

@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
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.

4 participants