JSON data exposed at human-readable URLs
JSON data for pull requests, commits, and releases is now accessible at clean URLs that mirror the site routes — no more digging through nested manifest paths.
Each pull request, commit, and release page on the site has a sibling JSON endpoint backed by the same data. Instead of guessing where story data lives, developers can fetch it directly at /pull/44.json, /commit/<sha>.json, or /releases/v0.1.5.json. The data manifests in the build output also gain a jsonUrl field on each entry, so programmatic consumers can discover endpoints without path construction.
The build pipeline runs a new post-build step that copies JSON files into their route-aligned locations and updates the manifests. Password-protected deployments remain secure — the encryption pass was updated to wrap the new JSON files in the same envelope format.
A bundle of React and workflow fixes landed alongside the feature. The preview deployment workflow was building from a released CLI version rather than the pull request source, so site changes in PRs never reached Vercel previews. That is fixed. React errors #310 and #300 were traced to history state handling in the panel provider — the fix preserves Next.js router internals during URL changes, moves synchronous URL updates out of animation callbacks, and corrects click interception to capture phase. Duplicate history entries from back/forward navigation are eliminated. Vercel deploys now bundle uploads with --archive=tgz to avoid per-file rate limits on large static exports.
In the @gitpulse/site app.