chore(ci): remove the Autopilot bulk-update-cli job [FSM-1137] - #17477
Open
pgragg wants to merge 1 commit into
Open
chore(ci): remove the Autopilot bulk-update-cli job [FSM-1137]#17477pgragg wants to merge 1 commit into
pgragg wants to merge 1 commit into
Conversation
FSM-1137. The job sent POST $AUTOPILOT_HOST/api/bulk-update-cli after each successful CLI publish, and it exits 1 when the response is not 2xx. The Autopilot service does not move to the Postman AWS account, so the CLI release workflow would turn red as soon as Autopilot stops answering. The publish itself completes in the earlier prod job. This job only started a fan-out of CLI version bump pull requests to onboarded config repositories. The job was the only user of vars.AUTOPILOT_HOST.
![nitpickybot[bot]](https://avatars.githubusercontent.com/in/2901896?s=60&v=4){kind=small}
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
FSM-1137. Remove the
bulk-update-clijob from the CLI release workflow.The job sent
POST $AUTOPILOT_HOST/api/bulk-update-cliafter each successfulCLI publish, with
AUTOPILOT_HOSTdefaulting tohttps://autopilot.buildwithfern.com.Research in FSM-352 shows that Autopilot must not move to the Postman AWS
account. The job is the last daily caller of Autopilot from this repository,
so it must go before Autopilot can be switched off.
Why this is safe
prodjob.bulk-update-cliruns after it and only starts a fan-out of CLI version bump pull requests to
onboarded config repositories.
1when the response is not 2xx. If we leave the job inplace, the CLI release workflow turns red on every publish as soon as
Autopilot stops answering. CLI publishes happen almost every day.
needs: [bulk-update-cli], so removing it does not changeany other job.
vars.AUTOPILOT_HOSTin this repository. Acode search for
AUTOPILOT_HOST,bulk-update-cli, andautopilot.buildwithfern.comreturns only this workflow.The
permissionsblock stays as it is.contents: readandid-token: writeare still needed for checkout and for OIDC publishing in the other jobs.
Effect on customers
Onboarded config repositories stop receiving an automatic CLI version bump
pull request. That fan-out was an early-access feature. It is blocked by
default by a per-repository PostHog flag, and only three of its pull requests
have merged into a named customer repository, the last one on 2026-05-12.
Not in this change
No infrastructure change. The Autopilot ECS services, RDS instance,
ElastiCache cluster, S3 buckets, Lambda function, and the
AUTOPILOT_*PostHog flags stay as they are.
The
"autopilot"value of theInvocationSourceIR enum stays. It is agenerated type, not a call to the service.
Test plan
Merge, then confirm that the next
Publish Fern CLIrun finishes green andmakes no request to Autopilot.
Ticket: https://postmanlabs.atlassian.net/browse/FSM-1137
Why this PR is in
fern-apifern-api/fernis the CLI and generators monorepo and has nopostman-engmirror, so a workflow change has to land here. Checked with
gh search code --owner postman-eng "pnpm seed publish cli"(empty) andgh search repos --owner postman-eng fern(nosdk-gen-fern).Review follow-ups
chore(ci): the diff only touches.github/workflows/.Both scopes pass
lint-pr-title.yml.diff:
gh api repos/fern-api/fern/actions/variableslists onlyTURBO_TEAM, sothere is no repository-level
AUTOPILOT_HOSTleft to delete. An org-levelvariable would still be readable by this workflow, but reading org variables
needs
admin:org, so someone with that scope should confirm.bulk-update-cli. Verified againstbranches/main/protectionand both rulesets (Mainline Protection,main),which require only
biome,lint,compile,depcheck,Validate versions.yml files,test,test-ete, and theseed-test-results (*)matrix. Removing the job cannot block a merge.Why this replaces #17473
Same branch, same one-file diff. #17473 had to be replaced, not reopened.
While applying review feedback I amended the commit message from
chore(cli)tochore(ci)inside a shallow clone (git clone --depth 1 --filter=blob:none).The shallow graft meant the amended commit was written with no parent, so the
pushed branch shared no history with
main, and GitHub closed #17473. GitHubthen refuses to reopen a pull request whose branch was force-pushed after it was
closed ("state cannot be changed").
The branch has been rebuilt from a full-history clone on top of
main(
65eb98d), so it is now one commit ahead ofmaintouching only.github/workflows/publish-cli.yml. The tree is byte-identical to the onereviewed in #17473.
Lesson recorded: never amend or rebase in a
--depth-limited clone.