Repository navigation
oakum 0.6.1
Fixed
Errors, warnings, prompts, and the summaries oakum status and oakum version print now escape bytes that could rewrite the terminal, such as an escape sequence or a bidi override in a bump file's name or a pnpm package name. So does the plan oakum ci pr-status prints to stdout when GITHUB_STEP_SUMMARY is unset; the job summary file keeps the text as rendered. Before, only some messages did: oakum status printed a bump file's name raw when refusing it, and the summaries printed such names raw. Error text quoted from pnpm, cargo, git or the old release tool prints without its colour codes. Combining accents print as written rather than as \u{301}. Output meant for scripts is unchanged: --json, and the paths, URLs and tags that commands print as their result.
oakum migrate runs bumpy, changesets and knope under OAKUM_REMOTE_DEADLINE like every other child: one whose answer has not arrived by then is named, and migrate exits 2 (unverified) instead of hanging.
migrate also finds those tools on PATH the way discovery finds pnpm, including a Git Bash PATH on Windows (/c/Users/..., or :-separated entries), which its lookup used to miss.
Both lookups now share one reading of PATH. On Windows, a quoted entry such as "C:\Program Files\knope" and a verbatim one such as \\?\C:\tools are each one directory, and only a name with a PATHEXT extension is taken, never an extensionless file. Elsewhere, PATH is read as the shell reads it, so /a/bin is a directory rather than drive A: and a bare pnpm wins over a pnpm.EXE beside it. On every system an empty PATH entry is skipped rather than read as the current directory, so it no longer runs a pnpm, bumpy, changeset or knope file from the repository being inspected.
Four messages now say what to do:
- A version no tag records (
never released, but the manifest is 1.0.0) names the tag to cut, rendered fromtag-formator the default:`git tag @demo/a/v1.0.0 <commit>`. Atag-formatwhose tag oakum could not read back as that version names none. - In
oakum check, a change with no covering intent namesoakum add --packages <package>:<level>, and, when conventional commits are on,oakum generate --from <base>over the rangecheckread. oakum addwithout--messagesays the bump file's changelog entry will be empty.oakum initandoakum migratesay why they reach GitHub when the lookup for the printed workflow's action pins fails, and that nothing was written.
Install oakum 0.6.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/oakoss/oakum/releases/download/v0.6.1/oakum-installer.sh | shInstall prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/oakoss/oakum/releases/download/v0.6.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.6.1Download oakum 0.6.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>