Skip to content

version string is reported inconsistently #5893

@nestor-custodio

Description

@nestor-custodio

Love the new -v / --version CLI flags, but I did notice the version text is not exactly the same when you issue a caddy version (which terminates the printed version string with a newline) and when you issue a caddy -v / caddy --version (which doesn't).

This is a very minor item, but it did break my update check automation when I updated it to run --version instead of version, and I imagine it might be an issue for other (more important) tooling elsewhere.


caddy version:

(0) nestor@compy9000 ~/links $caddy version
v2.7.5 h1:HoysvZkLcN2xJExEepaFHK92Qgs7xAiCFydN5x5Hs6Q=
(0) nestor@compy9000 ~/links $

caddy -v / caddy --version:

(0) nestor@compy9000 ~/links $caddy -v
v2.7.5 h1:HoysvZkLcN2xJExEepaFHK92Qgs7xAiCFydN5x5Hs6Q=(0) nestor@compy9000 ~/links $
(0) nestor@compy9000 ~/links $caddy --version
v2.7.5 h1:HoysvZkLcN2xJExEepaFHK92Qgs7xAiCFydN5x5Hs6Q=(0) nestor@compy9000 ~/links $

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions