-
MOXYTOOL v1.5.2
Stablereleased this
2026-10-02 14:05:46 +00:00 | 5 commits to main since this releaseFixes
- Moved the CLI to @push.rocks/smartconsole; commands, options, help banner and version output are unchanged; unknown commands, unknown options (for example
moxytool update --force) and options with an invalid value (for example a non-numericvgpu-setup --step) now exit 1 with an error instead of being ignored. - Script search now really ranks slug matches above name matches above description matches; the previous weighting read match data the search never returned, had no effect, and its type error blocked type-checked builds.
- The npm
postinstallscript downloads the platform binary only when the package is installed as a dependency (insidenode_modules); in the moxytool repository itself, including the release checkout, it skips the download, because that version's binaries are not released yet. It reads the version from its ownpackage.jsoninstead of falling back to 1.0.0, and the fallback URL to amasterbranch that never held the gitignored binaries is gone. - The release workflow finds the version's section under gitzone's
## <date> - <version>headings, so release notes are no longer empty, and its install command points at themainbranch.
Maintenance
deno.jsonsetsminimumDependencyAgeto seven days and excludes the owner npm scopes (@push.rocks/*,@serve.zone/*and the others), so Deno 2.9 resolves freshly released owner packages such as@push.rocks/smartconsolewhile third-party packages still wait a week.- Release tooling: the pnpm pin moves from 10.18.1 to 12.7.0, and the empty
npmextra.jsonbecomes.smartconfig.json, the file currentgitzonereads. - Release configuration:
gitzone releasepushes the branch and the version tag and publishes the npm package to verdaccio.lossless.digital and registry.npmjs.org; the tag workflowrelease.ymlbuilds the binaries and attaches them to the Gitea release. Thenpm-publish.ymlworkflow, which failed on every tag becausepublishConfig.registrypointed the npmjs publish at verdaccio, is removed, and so ispublishConfig.registry, so the registry comes from the release configuration alone. pnpm-lock.yamlis committed, so the release checkout installs withpnpm install --frozen-lockfile.- The empty
readme.hints.mdmoves out of the package root to the untracked.nogit/, so npm no longer packs it.
Downloads
- Moved the CLI to @push.rocks/smartconsole; commands, options, help banner and version output are unchanged; unknown commands, unknown options (for example