feat(cli): detect Postman deploy source from git commit message

[matlegault]

Description

Refs fern-api/fern-platform#9560 (companion PR)

Adds support for detecting when a docs deployment was triggered by a Postman collection update, by inspecting the git commit message for a [source:postman] marker. When found, the CLI includes deploySource: "postman" in the X-CI-Source JSON header sent to FDR during docs publishing, so the dashboard can show a Postman indicator in the deployment activity log.

This approach detects the source directly from the commit message rather than requiring a custom workflow step to set an env var — meaning it works for all existing Postman-integrated repos on day one without any workflow template changes.

Changes Made

• Added deploySource?: string field to the CISource interface (in all three locations where it's defined)
• Added detectDeploySource() helper that runs git log -1 --format=%s and checks for [source:postman] in the commit subject
• detectCISource() now calls detectDeploySource() only after a CI environment is confirmed — the git exec is never spawned on local dev machines
• Refactored detectCISource() from separate if blocks with early returns to an if/else if chain that builds a source object, then conditionally enriches it with deploySource
• The git call is wrapped in try/catch with a 5s timeout and stdio: "pipe" to prevent stderr from leaking to the user's terminal when git is unavailable
• Errors are logged at console.debug level for diagnosability
• Added versions.yml entry for v4.67.0 (minor bump for feat)

Testing

• Unit tests added/updated
• Lint passes (pnpm run check)
• Biome passes (pnpm check:biome)
• Manual testing completed

Reviewer Checklist

• Synchronous shell exec: detectDeploySource() uses execSync which blocks the event loop. The 5s timeout bounds the worst case, and this only runs once per CLI invocation and only when already inside a recognized CI environment. Worth confirming this is acceptable.
• Commit message detection scope: git log -1 --format=%s reads the HEAD commit subject. For merge commits or squash merges, verify the [source:postman] marker propagates to the final commit subject (the fern-platform companion PR controls the commit message format).
• Three CISource interfaces: The field was added to all three duplicate definitions (environment.ts, publishDocs.ts, runRemoteGenerationForDocsWorkspace.ts). The duplication is pre-existing.
• No unit tests: detectDeploySource() shells out to git so it's not easily unit-testable without mocking execSync. The function is small and defensive (try/catch + timeout). Consider whether integration coverage is sufficient.
• Backward-compatible: The field is optional and only included when the marker is detected, so existing deployments are unaffected.
• FDR compatibility: deploySource is a new non-URL string field in the X-CI-Source JSON. FDR's sanitizeCiSource only strips URL fields (runUrl), so this passes through untouched. No FDR changes needed.

Updates since last revision

• Deferred detectDeploySource(): Moved the execSync git call so it only runs after a CI environment (GitHub/GitLab/Bitbucket) has been confirmed. Previously it ran unconditionally at the top of detectCISource(), which could block local dev machines for up to 5s with no benefit.
• Refactored control flow: Changed detectCISource() from separate if blocks with early returns to if/else if chain, building a source variable that gets enriched with deploySource before returning.
• Version bumped to 4.67.0: Main branch added its own 4.66.0 entry, so our entry is now 4.67.0.

Link to Devin session: https://app.devin.ai/sessions/9b2a038d4ebb47039520482f78e4a254
Requested by: @matlegault

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[claude]

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.

_{Tip: disable this comment in your organization's Code Review settings.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[graphite-app]

The createdAt date for version 4.66.0 is "2026-04-08", which is earlier than the createdAt date of the older version 4.65.3 ("2026-04-10"). This creates a chronological inconsistency where a newer version has an earlier creation date than an older version.

If the versioning system or changelog relies on chronological ordering, this could cause issues with:

• Version sorting/ordering
• Changelog generation
• Release timelines

Fix: Update the createdAt date to match or be later than the current date:

createdAt: "2026-04-10"

Suggested change

	createdAt: "2026-04-08"
	createdAt: "2026-04-10"

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 6 additional findings in Devin Review.