curl -fsSL https://release-notes.eu/install.sh | shInstall the binary, run the init command in a repository, and commit the file it creates. From then on anyone who checks out the repository can reach the same toolchain with a single command. The init command detects common project layouts and pre-fills what it can; everything it guesses is marked with a comment so you know what to review.
The configuration is a single file at the repository root. It has three top-level sections: the toolchain to provide, the environment variables to export, and the commands to expose. Anything not listed is not available inside the managed environment, which is the point. Unknown keys are an error rather than a warning, so a typo fails fast instead of silently doing nothing.
Resolution writes a lockfile with exact versions and checksums. Commit it. On a machine with the lockfile present, resolution is skipped entirely and the recorded versions are used. Refreshing is an explicit command, never a side effect of running something else.
The cache directory is the only state worth persisting between runs. Point the cache at your CI cache directory and restore it by lockfile hash. A cold run downloads everything; a warm run touches no network. Both produce identical environments, which is the property that makes a failing build reproducible on a laptop.
Point the registry setting at your own host and supply a token through the environment. The tool never writes credentials to disk and never embeds them in the lockfile. Checksums are verified regardless of where an artefact came from.