Install and update Kyna

Kyna publishes native ky archives, the kyna 1.x compatibility alias, per-user installers, a VS Code extension, and a Linux container from protected release tags.

Install the current preview

The official npm package is the recommended path:

1npm install --global @kyna-language/cli@preview

The npm package version is locked to the GitHub release tag. Its postinstall script downloads the same native archive and SHA256SUMS, restricts redirects to GitHub release hosts, verifies the archive, and exposes both ky and kyna. It does not compile Kyna on the user's machine or require a repository clone.

Bun users must explicitly trust the package so Bun runs that verified postinstall step:

1bun add --global --trust @kyna-language/cli@preview

The published JavaScript command shim currently requires Node.js 18+ even when Bun performs the installation.

Install the same preview directly on macOS or Linux without a JavaScript package manager:

1curl -fsSL https://github.com/Up-to-code/Kyna/releases/download/v1.0.0-preview.3/install.sh | sh -s -- --channel preview --version 1.0.0-preview.3

Windows PowerShell:

1& ([scriptblock]::Create((irm 'https://github.com/Up-to-code/Kyna/releases/download/v1.0.0-preview.3/install.ps1'))) -Channel preview -Version 1.0.0-preview.3

Preview scripts require an explicit version so they never resolve an unsigned prerelease through the stable channel.

Versions and updates

1npm install --global @kyna-language/cli@preview         # install or update preview
2npm install --global @kyna-language/cli@1.0.0-preview.3 # exact preview
3npm outdated --global @kyna-language/cli                # inspect available updates

After the first signed stable release, omit the tag or use @kyna-language/cli@latest.

The release action derives the npm version from the Git tag, downloads and executes the newly published GitHub binary as a smoke test, and then publishes that immutable npm version. A stable tag advances npm's latest distribution tag; a prerelease tag advances preview. Re-running a completed version repairs its distribution tag instead of attempting to overwrite the published package.

The Git tag is the release trigger and version source. Push a tag matching the version declared by the root CMake project, or manually run the release workflow while selecting that existing tag:

1git tag v1.0.0
2git push origin v1.0.0

No npm manifest version edit is required. The action rejects a tag whose base semantic version differs from the compiler project version.

Unix defaults to ~/.local; Windows defaults to %LOCALAPPDATA%\Kyna. Both installers detect the OS and architecture, download the exact native archive over HTTPS, verify SHA256SUMS before extraction, install atomically, and retain the previous executable for rollback. Use --prefix, --version, --channel stable|preview, and non-interactive mode as needed. A preview requires an explicit version.

ky self update invokes the same verified installer contract. ky self uninstall removes only the Kyna executables under the resolved per-user prefix.

This is the current zero-clone installation path. Homebrew, Scoop, WinGet, and Linux repository manifests are distribution adapters to add after hosted-runner release validation is complete. They must install the same versioned archives and preserve the checksum/signature policy rather than introducing separately built binaries. A rustup-style toolchain manager is deferred until Kyna supports multiple compiler channels or versions concurrently; the present installer and ky self interface are the smaller, deeper solution.

Release assets

• kyna-darwin-arm64.tar.gz
• kyna-darwin-x86_64.tar.gz
• kyna-linux-arm64.tar.gz
• kyna-linux-x86_64.tar.gz
• kyna-windows-x86_64.zip
• kyna-language-support-<version>.vsix
• install.sh, install.ps1, SHA256SUMS, and the canonical @kyna-language/cli npm package
• GitHub build-provenance attestations

Each CLI archive contains bin/ky, the bin/kyna alias, templates, the license, documentation, and runnable examples. Stable macOS binaries are Developer ID signed and notarized; stable Windows binaries are Authenticode signed. Missing signing credentials block a stable release. Unsigned tagged builds must be marked prerelease and installed with an explicit version.

Container and Dev Container

Tagged releases publish ghcr.io/up-to-code/kyna:<version> for Linux amd64 and arm64. The image runs as a non-root user and exposes port 3000; the application must explicitly choose 0.0.0.0 when container ingress is intended. Native binaries remain the primary experience.

The repository’s .devcontainer definition installs ky, recommends the Kyna VS Code extension, enables format-on-save, and forwards port 3000.

VS Code

tools/package-vscode.sh uses official @vscode/vsce. Source README artwork remains repository-relative for GitHub, while release packaging rewrites it to a release-tag-specific HTTPS base. Validation rejects relative packaged images, missing grammar/snippet/example/icon assets, and—during a tagged release—any image URL that does not return HTTP 200.

Install a downloaded package with:

1code --install-extension kyna-language-support-<version>.vsix --force

Marketplace publication is enabled only when the repository has a publisher-scoped VSCE_PAT secret.

Release and documentation cadence

A weekly maintenance review may refresh research records, implementation status, compatibility notes, examples, and benchmark baselines. It does not promise a weekly binary release. Documentation must describe the checked-in implementation and release policy; forward-looking work remains labeled as planned or deferred.