Skip to content

[Backport release-2.3] docs: Enclose the CLI version number in backticks#56

Merged
phisco merged 1 commit into
release-2.3from
backport-55-to-release-2.3
May 30, 2026
Merged

[Backport release-2.3] docs: Enclose the CLI version number in backticks#56
phisco merged 1 commit into
release-2.3from
backport-55-to-release-2.3

Conversation

@github-actions
Copy link
Copy Markdown

Description

Backport of #55 to release-2.3.

At the top of our generated docs we have a line like:x

```
This documentation is for the `crossplane` CLI v2.4.0-rc.0.10.gb96ad2d.
```

When using a development build (no version number) or a build with a proper
version number (v2.3.1), this is fine. But when using a main branch build like
the example above, the version number triggers some vale linter errors.

Enclose the version number in backticks (make it inline code) so that vale will
ignore it. This will look fine in the rendered docs as well.

Signed-off-by: Adam Wolfe Gordon <awg@upbound.io>
(cherry picked from commit da5165c)
@github-actions github-actions Bot requested review from a team, jcogilvie and tampakrap as code owners May 29, 2026 22:33
@github-actions github-actions Bot requested review from phisco and removed request for a team May 29, 2026 22:33
@adamwg adamwg closed this May 29, 2026
@adamwg adamwg reopened this May 29, 2026
@phisco phisco merged commit ee2a859 into release-2.3 May 30, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants