[Tonours]

The API reference now deploys from the tip of main only, one deploy at a time.

What

File	Change
.github/workflows/build.yml	publish-api-reference gets concurrency: pages-${{ github.ref }} (cancel-in-progress: false) and a first step that compares github.sha with the current tip of the branch. Not the tip: Setup Pages and the deploy are skipped with a notice, and the job stays green.

Why

• Four PRs merged within a minute today. The run for d57be6091 hit the deploy while the newer 9a884d4e6 was already deploying, and GitHub refused it: 400 ... due to in progress deployment (run 39978461570).
• Concurrency alone is not enough. That older run reached the deploy after the newer one, so serialized it would have waited, then overwritten the fresh reference with stale docs. The tip check kills that case: only the newest run publishes, same idea as the release job draining the backlog from the tip.

How to test

• actionlint (docker rhysd/actionlint) on build.yml: same 2 pre-existing findings before and after, none on these lines.
• gh api repos/ForestAdmin/agent-nodejs/git/ref/heads/main --jq .object.sha run locally returns the tip SHA.
• Not run on main yet: the next burst of merges is the real test (older runs should show the skip notice, the tip run deploys).

Definition of Done

General

• Write an explicit title for the Pull Request, following Conventional Commits specification
• Test manually the implemented changes
• Validate the code quality (indentation, syntax, style, simplicity, readability)

Security

• Consider the security impact of the changes made

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[PMerlet]

Spec (no ticket: the PR description): conforms.

[PMerlet]

Approved after /validator run 2038-20261023165727-PMerlet: nothing blocking posted, 0 preferential or code style, 0 suppressed below all.