Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/publish-fern-docs.yml:
- Line 93: The yq slice expression used to set PRUNED contains an extra dot
before the array projection; update the PRUNED assignment so the expression
removes the stray dot — change the selector from
".products[0].versions[$KEEP:].[].slug" to use
".products[0].versions[$KEEP:].[].slug" (i.e., edit the PRUNED=$(yq "...") line
to the corrected selector).

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/publish-fern-docs.yml:
- Around line 106-116: The script currently checks for changes before running
git add which misses newly created files; instead stage the files first (git add
fern/versions/ fern/docs.yml) and then test for staged changes using git diff
--cached --quiet (or git diff --staged --name-only) to decide whether to commit;
update the flow around TAG_VERSION and MAX_VERSIONS so the code only runs git
commit -m "chore(fern): register ${TAG_VERSION}, keep latest ${MAX_VERSIONS}
versions [automated]" and git push origin main when the staged-diff check shows
changes.
- Line 74: The yq mutation assumes .products[0].versions[0] is the "Latest"
entry, so add a pre-check that inspects .products[0].versions[0]."display-name"
(or searches .products[0].versions for the entry with "display-name": "Latest")
and aborts or adjusts if it isn't found; update the step that runs the yq
command (the existing yq -i '.products[0].versions |= [.[0]] + [{"display-name":
env(TAG_VERSION), "path": "versions/" + env(TAG_VERSION) + ".yml", "slug":
env(TAG_VERSION), "availability": "stable"}] + .[1:]' fern/docs.yml) to only run
when the validation passes (or compute the correct index and insert after the
located "Latest" element), so insertion reliably places the new version after
the actual "Latest" entry.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/publish-fern-docs.yml:
- Around line 55-56: The current tag gate uses startsWith/contains which lets
non-exact semver tags pass; update the three mutating steps' if: conditions (the
"Register new version from tag", "Prune old versions", and "Commit version
changes" steps) to also require the ref matches an exact semver tag using GitHub
expressions, e.g. require github.ref matches '^refs/tags/v\\d+\\.\\d+\\.\\d+$'.
Alternatively compute a single boolean once (e.g. set job output like
is_exact_semver) using that regex and reuse it in the three steps' if:
conditions; change the if: on the existing steps (the lines with
startsWith(github.ref, 'refs/tags/v') && !contains(github.ref, '-')) to include
the matches(...) check or job-output reference.

---

Duplicate comments:
In @.github/workflows/publish-fern-docs.yml:
- Around line 50-53: The checkout step currently pins with.ref: main which
results in a shallow clone missing tag refs needed later by git archive
"${TAG_VERSION}" and git show-ref refs/tags/..., so update the actions/checkout
step (the uses: actions/checkout entry) to fetch tags and full history — e.g.,
remove the hard ref or add with: fetch-depth: 0 (and/or fetch-tags: true) so tag
refs are present locally before any tag-based git operations.