Releases: yontrack/yontrack-cli
Releases · yontrack/yontrack-cli
Release list
5.6.0
5.5.0
Features
- #60 brew: install the CLI from a Homebrew tap
5.4.3
Bugs
- #65 install: the default install dir needs privileges on a stock macOS
5.4.2
Bugs
- #64 project list: fails to decode because project ID is typed as int instead of string
5.4.1
Enhancements
- #56 docs: add a CONTEXT.md glossary
- #57 docs: ADR for declining macOS notarization
- #58 ci: no linting of the shell scripts
- #59 ci: nothing verifies that install.sh works
- #62 build: nothing checks what a release actually publishes
Bugs
- #63 docs: the CLI still calls itself the Ontrack CLI
5.4.0
Features
- #53 install: one-line installer script
Enhancements
- #49 build: drop the ontrack-cli-* compatibility binaries
- #51 build: no linux/arm64 binary is published
- #52 release: publish checksums for the release assets
- #54 docs: README still calls the product Ontrack
- #55 docs: installation instructions omit chmod and the macOS quarantine dialog
- #56 docs: add a CONTEXT.md glossary
- #58 ci: no linting of the shell scripts
Bugs
5.3.0
Move references to the yontrack/yontrack-cli repository The repository has been transferred from nemerosa/ontrack-cli to yontrack/yontrack-cli, which changes three things that were pinned to the old home. The CI credentials no longer resolve: ONTRACK_URL and ONTRACK_TOKEN came from the nemerosa organisation and do not follow a transfer. The yontrack organisation names them YONTRACK_URL and YONTRACK_TOKEN, as used throughout yontrack/yontrack, so both workflows now reference those. The release workflow pinned `--project ontrack-cli` as a literal, while go.yml lets Yontrack derive the project from GITHUB_REPOSITORY. After the transfer those two would resolve to different projects and the changelog export would find no build. It now derives the project the same way, from the repository name, so a future rename carries itself. The README build badge and releases link pointed at nemerosa/yontrack, a repository that has never existed - both 404ed before this change. The GitHub setup example used the same dead path as its sample value; the main product now lives at yontrack/yontrack. The ontrack-cli-* release assets are deliberately left in place: one migration at a time. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5.2.0
Enhancements
5.1.1
5.1.0
Other
- #40 Support for promotion run fields