• v1.5.2 53f9059a61

    MOXYTOOL v1.5.2
    CI / Type Check & Lint (push) Successful in 2m19s
    CI / Build Test (Current Platform) (push) Successful in 2m33s
    Release / build-and-release (push) Successful in 9m39s
    CI / Build All Platforms (push) Successful in 10m31s
    Stable

    jkunz released this 2026-10-02 14:05:46 +00:00 | 5 commits to main since this release

    Fixes

    • 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-numeric vgpu-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 postinstall script downloads the platform binary only when the package is installed as a dependency (inside node_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 own package.json instead of falling back to 1.0.0, and the fallback URL to a master branch 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 the main branch.

    Maintenance

    • deno.json sets minimumDependencyAge to 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/smartconsole while 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.json becomes .smartconfig.json, the file current gitzone reads.
    • Release configuration: gitzone release pushes the branch and the version tag and publishes the npm package to verdaccio.lossless.digital and registry.npmjs.org; the tag workflow release.yml builds the binaries and attaches them to the Gitea release. The npm-publish.yml workflow, which failed on every tag because publishConfig.registry pointed the npmjs publish at verdaccio, is removed, and so is publishConfig.registry, so the registry comes from the release configuration alone.
    • pnpm-lock.yaml is committed, so the release checkout installs with pnpm install --frozen-lockfile.
    • The empty readme.hints.md moves out of the package root to the untracked .nogit/, so npm no longer packs it.
    Downloads