Releases
Releases are published on GitHub, each with archives for every platform, checksums.txt and a changelog. The same version is published to npm as @kheif/quiver.
Versions
Section titled “Versions”Versions follow v<major>.<minor>.<patch>. A tag with a suffix, such as v1.3.0-rc.1, is a prerelease: GitHub marks it so, the install scripts' "latest" skips it, and npm publishes it under the next tag.
To install a given version:
curl -fsSL https://raw.githubusercontent.com/kheif/quiver/main/install.sh | QUIVER_VERSION=v1.2.0 shnpm install -g @kheif/quiver@1.2.0The docs follow the main branch
Section titled “The docs follow the main branch”This website is built from the main branch. Features that are on main but not in the latest release are marked Next release, with what differs in the latest release.
How a release is made
Section titled “How a release is made”A version tag starts the release workflow. It runs the tests and govulncheck, builds the archives with GoReleaser, publishes the GitHub release and the npm packages, then installs the release on clean Linux, macOS and Windows machines with each install method. The process is described in docs/releasing.md.
License
Section titled “License”Quiver is licensed under the Apache License 2.0.