Repository navigation
Release Notes
- A profile's credentials only go to the server it was saved for. A command that uses a profile with
--regionor
--hostfor another server now fails instead of sending them there. - A command that runs while you log in to the same profile again, on another server, uses the profile's old server and
old login, or both new ones. Before, it could send the new login's token to the old server. docspring loginwithout--regionor--hostusesDOCSPRING_REGIONorDOCSPRING_HOSTfor a new profile, as
commands do with an API token in the environment.- Logging in again to a
--hostprofile uses the--issuerits last login was given. - A profile saved by a newer version of the CLI no longer stops your other profiles from working, and saving another
profile keeps it. docspring submitanddocspring submissions downloadcheck each file's size as well as its SHA-256 checksum, so a
file the API lists without a checksum (an audit trail made before September 2024) is checked too.
Install docspring-cli 1.0.1
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/DocSpring/docspring-cli/releases/download/v1.0.1/docspring-cli-installer.sh | shInstall prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/DocSpring/docspring-cli/releases/download/v1.0.1/docspring-cli-installer.ps1 | iex"Install prebuilt binaries via Homebrew
brew install DocSpring/tap/docspringDownload docspring-cli 1.0.1
| File | Platform | Checksum |
|---|---|---|
| docspring-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| docspring-cli-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| docspring-cli-aarch64-pc-windows-msvc.zip | ARM64 Windows | checksum |
| docspring-cli-x86_64-pc-windows-msvc.zip | x64 Windows | checksum |
| docspring-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| docspring-cli-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 DocSpring/docspring-cliYou 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> --repo DocSpring/docspring-cli