Documentation Index
Fetch the complete documentation index at: https://mintlify.com/SGizek/Raiku/llms.txt
Use this file to discover all available pages before exploring further.
raiku pin lets you lock a package at a specific version so that raiku update --all skips it entirely. Pinning is useful whenever a package serves as a stable baseline — a library whose API your code depends on, a toolchain at a known-good version, or a package you are evaluating before committing to an upgrade. Pins are recorded in ~/.raiku/pins.json and persist across sessions.
Usage
Subcommands
| Subcommand | Description |
|---|---|
add PACKAGE [VERSION] | Pin PACKAGE at VERSION. If VERSION is omitted, the currently installed version is used. |
remove PACKAGE | Remove the pin from PACKAGE, allowing future updates. |
list | Show all currently pinned packages with version, date, and reason. |
Flags for add
| Flag | Description |
|---|---|
--reason TEXT | Optional note stored alongside the pin explaining why it was created. |
Behavior
- Pinned packages are skipped by
raiku update --all. Raiku will print a notice that the package is pinned and move on. - Pinned packages can still be updated explicitly by naming them directly (
raiku update fast-math) and using--forceif needed. - The pin stores the version string at the time
pin addis called. If you later install a different version manually, you may want to re-pin with the new version. - Pin storage:
~/.raiku/pins.json— a JSON file keyed by lowercase package name containing the pinned version, timestamp, and optional reason.
Examples
Sample raiku pin list output
Pin storage format (~/.raiku/pins.json)
Pins are per-machine — they live in
~/.raiku/pins.json and are not committed to source control. If you want reproducible installs across machines, use raiku from-lock with a committed raiku.lock file instead of relying solely on pins.