Versions and updates
Rivet is published on npm as @agilno-tech/rivet. Install without a version to select npm’s latest tag. Rivet is still alpha software; the tag does not mean a stable release. The first published version is 0.1.0-alpha.0.
Update Rivet
Inside your project, run:
rivet update
rivet --versionSee Updating Rivet for the one-time update from older versions, project runtime pins, scope options and manual package-manager commands.
The default latest tag moves forward when a new release is published. Append an exact published version, such as @0.1.0-alpha.0, when your team needs the same version. The legacy alpha tag is not updated by automation; reinstall without @alpha to receive current releases. Project-only, verified-tarball and advanced source installations have separate installation instructions.
Review active tasks and keep your project configuration, private task state and worktrees before updating. Do not delete unfinished work to resolve an upgrade problem. Older versions may not understand newer task state; downgrades are not guaranteed.
See release notes and compatibility. Maintainers preparing a package should use the release procedure.
License
Rivet is licensed under Apache License 2.0. Preserve the license and applicable attribution notices when redistributing it.