Repository navigation
oakum 0.5.1
Fixed
Discovery's cargo metadata, pnpm root -w and pnpm list, and the pnpm --version that init and migrate run, now run under the same wall-clock deadline as oakum's git children: five minutes, or OAKUM_REMOTE_DEADLINE seconds, per child. A child that never answered, for example cargo metadata blocked opening a member Cargo.toml that is a FIFO, used to hang every command that discovers packages with no output, the CI version job included. Oakum now kills it at the deadline and reports the look as unverified (exit 2), naming the tool and the variable. A malformed OAKUM_REMOTE_DEADLINE, which discovery used to ignore, now leaves discovery unverified too, as it already did for git. When one tool times out and the other fails outright, the failure decides (exit 1). If cargo or pnpm is a wrapper that starts the real tool as its own child, the real tool can outlive the kill.
A git call that never answers now leaves the run unverified (exit 2): one killed at OAKUM_REMOTE_DEADLINE, or one whose output stalled or could not be read. The exit used to follow the kind of call, so a hung git log made check --strict exit 1, a hung merge-base made version and status exit 1, and a hung config probe, the first git call a command makes, made version exit 1, each reporting a failure where nothing was settled. ci version-pr keeps exit 2 when it adds context to a git error, and the release changelog read keeps a call that never answered unverified while still refusing one that answered with a failure.
release re-checks a git tag or git push that never answered. When the tag is found locally, or the push on the remote, it stops with exit 1 and names the stage (tagged or pushed); when the tag is not there, the stage is the one before. Only when the re-check fails too is the stop unverified (exit 2). A git tag that never answered no longer reports completed: none over a tag it wrote. The detail under an unverified stop says unverified once, not twice.
A git that cannot be started, or that answered with a failure, keeps its exit.
Update rustls to 0.23.46 for RUSTSEC-2026-0346, -0347, -0348, and -0349, along with other semver-compatible dependency updates. serde-saphyr is capped below 1.3, so cargo install oakum without --locked keeps reading an empty block scalar (core: |) in a pnpm catalog as unresolved.
Install oakum 0.5.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/oakoss/oakum/releases/download/v0.5.1/oakum-installer.sh | shInstall prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/oakoss/oakum/releases/download/v0.5.1/oakum-installer.ps1 | iex"Install prebuilt binaries via Homebrew
brew install oakoss/tap/oakumInstall prebuilt binaries into your npm project
npm install @oakoss/oakum@0.5.1Download oakum 0.5.1
| File | Platform | Checksum |
|---|---|---|
| oakum-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| oakum-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| oakum-x86_64-pc-windows-msvc.zip | x64 Windows | checksum |
| oakum-aarch64-unknown-linux-gnu.tar.xz | ARM64 Linux | checksum |
| oakum-x86_64-unknown-linux-gnu.tar.xz | x64 Linux | checksum |
| oakum-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo oakoss/oakumYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>