Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion cmd/root.go
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ import (
// overridden at release with the git tag via -ldflags "-X .../cmd.version=vX.Y.Z".
// ferry uses SemVer with a leading v; an untagged build reports the line in
// progress (the -dev suffix marks it as not a tagged release).
var version = "v0.4.0-dev"
var version = "v0.8.0-dev"

var rootCmd = &cobra.Command{
Use: "ferry",
Expand Down
2 changes: 1 addition & 1 deletion docs/how-to/cutting-a-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ the CLI surface may still change between minor versions (pre-1.0 = not yet API-s
`v1.0.0` marks the first stable surface. The tag drives everything: the release
workflow triggers on `v*`, and the tag is stamped into the binary via `-ldflags` so
`ferry --version` reports it (e.g. `ferry v0.1.0`). Un-tagged local builds report the
current development line (`v0.4.0-dev`).
current development line (`v0.8.0-dev`).

Checksums are **automated**, not hand-pasted. A script computes the SHA256 of each
binary into a `checksums.txt` manifest that ships as a release asset; CI runs that
Expand Down
Loading