v0.2.1 — triago --version

The new bug report template asks for triago --version as its first required field. Until now the package had no such flag — it printed a page of usage text instead, so a public form was asking for something the software could not produce.

The version was previously reachable only through triago status, which needs the server running. That made it unavailable in exactly the situation it is wanted: reporting a bug where the server will not start.

It is answered before the command switch rather than inside it, because argument parsing routes anything beginning with -- into flags, so --version never reached the switch at all. -v and a bare version work too — this is the first thing a stranger types, and being clever about which spelling is correct helps nobody.

Also in this release

• The changelog now ships in the package. It was on GitHub only, so anyone who found triago through npm had to leave for the repository to see what changed between versions.
• Prettier is enforced in CI, so style is settled by a formatter rather than in review. Rewrapping only; no behaviour changed.
• The repository grew a contribution guide, a code of conduct, issue and pull request templates, and an OpenSSF Best Practices passing badge — all 67 criteria answered, including two answered Unmet because there is no coverage instrumentation and no dynamic analysis, which is the truth.

npm i -g @triago/cli

Requires Node 20 or newer. No schema, card-format or API change.