Conversation
No GitHub release ships a Windows binary. The install card and llms.txt said that one does. They now name macOS and Linux only. The JSON-LD operatingSystem field does not change, because the CLI builds for Windows and go install is a Windows install path. The FAQ and the catalog heading said that the catalog is generated on every merge to main. The deploy workflow builds the CLI from the latest release tag, so a command merged after a release appears only with the next release. The New tag marks the commands that the latest release added, and a release that adds none clears every tag. The FAQ, its FAQPage JSON-LD copy, and the heading now say this. Co-Authored-By: Claude Opus 5.5 <[email protected]>
grahampugh
approved these changes
Sep 24, 2026
ktn-jamf
enabled auto-merge (squash)
September 25, 2026 16:40
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The showcase site made two claims that are not true. This PR corrects them.
No Windows release binary
The install card on the site and the generated
llms.txtsaid that GitHub Releases ship a Windows binary. No release has a Windows asset. To check a release, rungh release view <tag> --json assets. Both places now name macOS and Linux only.How current the catalog is
The FAQ answer "How current is this catalog?" and the catalog heading said that the catalog is generated on every merge to
main. That is not how the deploy works:.github/workflows/deploy-site.yamlbuilds the CLI from the latest release tag. Frommain, it takes only the site files, the site generator, andinternal/commands/groups.go. A command merged after a release appears only with the next release.transformCommandsingenerator/site/main.gomarks as New the commands that the previous deploy did not have. It keeps that list while the version stays the same. A release that adds no commands clears every New tag.The visible FAQ, its FAQPage JSON-LD copy, and the catalog heading now say this.
Not changed
operatingSystemfield still lists Windows. This field says that the CLI runs on Windows, not that a release binary exists.GOOS=windows go build ./cmd/jamf-clisucceeds, andgo installis a Windows install path.README.mdstill says that the site is "Auto-updated on every merge." A fix for this sentence is outside the scope of this PR.Verification
go test ./generator/site/make verify-sitemake verify-site-output. This target also checks that the visible FAQ matches the FAQPage JSON-LD.make site, then a check of the page in a browser.🤖 Generated with Claude Code