.github/workflows/publish-fern-docs.yml (1)

93-93: 💤 Low value

Minor inconsistency with preview workflow's tag verification.

This step uses bare ref resolution (git rev-parse "$version"), while the preview workflow at line 69 uses explicit tag verification (git rev-parse -q --verify "refs/tags/$version"). Both work in practice since version names like v1.5.0 are typically only tags, but the explicit form is more precise and guards against accidentally matching a branch with the same name.

Consider aligning with the preview workflow for consistency:

🔧 Suggested change

-           if git rev-parse "$version" >/dev/null 2>&1; then
+           if git rev-parse -q --verify "refs/tags/$version" >/dev/null 2>&1; then

🤖 Prompt for AI Agents

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

In @.github/workflows/publish-fern-docs.yml at line 93, The tag-existence check
currently uses a bare ref resolution (git rev-parse "$version"); update the
check to the explicit tag verification used in the preview workflow by using git
rev-parse -q --verify "refs/tags/$version" so it only matches tags (not
branches) when evaluating the variable version; replace the condition around the
git rev-parse call accordingly where the step performs the tag verification.

.github/workflows/publish-fern-docs.yml (1)

73-85: 💤 Low value

Consider adding a pull/rebase before push for robustness.

The push on line 85 could fail if main moves between checkout and push (e.g., external commits). While the concurrency control helps prevent races within this workflow, external pushes to main could still cause failures.

This is acceptable for infrequent tag-push automation since failed runs can be retried, but adding a pull before push would improve resilience.

♻️ Optional: pull before push

          git config user.name "github-actions[bot]"
          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
          git add fern/versions/ fern/docs.yml
          git commit -m "chore(fern): add ${TAG_VERSION} version entry [automated]"
+          git pull --rebase origin main
          git push origin main

🤖 Prompt for AI Agents

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

In @.github/workflows/publish-fern-docs.yml around lines 73 - 85, The
commit-and-push step that runs TAG_VERSION and executes git push origin main can
fail if origin/main changed after checkout; update the block that configures git
user and runs git add/commit (the step named "Commit new version entry") to
fetch and rebase the latest main before pushing (e.g., run git fetch origin &&
git rebase origin/main or git pull --rebase origin main), handle non-zero exit
(abort/exit with message) if rebase fails, and only run git push origin main
after a successful fast-forward/rebase to avoid push conflicts.