Repository navigation
feat!: sync the OpenAPI spec with the production spec (EMSR-2795) - #1031
Merged
Merged
Conversation
Download the production OpenAPI spec and regenerate the resource commands. The last sync was on 2026-11-02. The sync adds the flag-release-plans-beta and environment-release-plans-beta command groups, and the scheduled-change commands in the segments group. Ticket: EMSR-2795. BREAKING CHANGE: The production spec removed the "Release policies (beta)" tag. The release-policies-beta command group no longer exists. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
katc1004
marked this pull request as ready for review
November 16, 2026 19:59
katc1004
requested review from
a team and
nieblara
and removed request for
a team
November 16, 2026 20:00
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 50aeaae. Configure here.
joannerd
reviewed
Nov 16, 2026
joannerd
reviewed
Nov 16, 2026
joannerd
reviewed
Nov 16, 2026
…ault The generated names replace-default and delete-default describe a PUT and a DELETE on a plan. These operations set or clear which plan is the environment's default, so the names follow the operation summaries. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
joannerd
approved these changes
Nov 16, 2026
nieblara
approved these changes
Nov 17, 2026
katc1004
deleted the
kchern/EMSR-2795/sync-openapi-flag-release-plans
branch
November 17, 2026 18:53
ld-ahartmann
approved these changes
Nov 17, 2026
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
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.

Summary
The flag release plans API went public on 2026-11-13 (launchdarkly/gonfalon#78896, EMSR-2718). The vendored
ld-openapi.jsonis from the 2026-11-02 sync (#963), so ldcli has no commands for it and the dailyCheck OpenAPI updatesjob fails. Ticket: EMSR-2795.Changes
I ran
make openapi-spec-downloadand the resource generator (go run resources/gen_resources.gofromcmd/). I did not commit the dev server regen frommake generate. That output does not compile, and #969 fixes it separately. Its input is the dev server's ownapi.yaml, so it is not related to this sync.New command groups:
flag-release-plans-beta:list,get,create,update,deleteenvironment-release-plans-beta:list,get,create,replace,delete,get-default,set-default,clear-defaultThe
segmentsgroup getslist-scheduled-changes,get-scheduled-change,create-scheduled-change,update-scheduled-change, anddelete-scheduled-change.Other changes from the same spec download:
agent-control list-agent-skillsgets a--sortflag, andaudit-log create-entriesgets a--rollupflag. Nine other generated blocks change only their description text:agent-control list-agent-optimizations,experiments update,feature-flags update, the fourintegrations-betacommands, and theenvironment-releases-betaandsegmentsgroup descriptions.Both new groups send the
LD-API-Version: betaheader on every request.One hand-written change: two entries in
mapOperationIdToCmdUsename the default release plan commandsset-defaultandclear-default. The generated names werereplace-defaultanddelete-default, which describe a PUT and a DELETE on a plan. These operations set or clear which plan is the environment's default, so the names follow the operation summaries.One naming note: the flag release plan
PUTbecomesupdate, and the environment release planPUTbecomesreplace. The generator maps the operation idsupdateFlagReleasePlanandPutEnvironmentReleasePlanby their verb. A rename of the operation id is a breaking change for every generated API client, so I left it as is.Breaking changes
The production spec removed the "Release policies (beta)" tag, so this command group goes away:
release-policies-beta(list,get-release-policy,create-release-policy,replace-release-policy,delete-release-policy,create-order)No hand-written code in this repository refers to the removed commands. The commit carries a
BREAKING CHANGEfooter for release-please.Testing
Automated Tests
go build ./...,go test ./...(64 packages), andgolangci-lint runpass. A second run of the generator on the committed tree leaves no diff, soscripts/check-openapi-changed.shreports "The OpenAPI has not changed."Manual Tests
I ran every
flag-release-plans-betacommand against the catamorphic instance, projectkathytest, with a throwaway plan that I deleted at the end:environment-release-plans-beta list --project kathytest --environment productionalso returns 200.To test it yourself, build with
make buildand run the commands above against a project in an account that has theenable-flag-release-plansflag. Without the flag, every call returns 404.Rollout
This is a generated-code change with no hand-written logic. The risk is the removal of the
release-policies-betagroup. The public spec no longer documents the release policies API, but the API is deprecated, not removed. If you still call it with ldcli, pin ldcli 3.16.0 or call the API directly.Release-please PR #1002 (4.0.0) is open and is already a major bump from #963. If this PR merges before 4.0.0 is cut, both breaking changes ship in one major version. If the team prefers to release 4.0.0 first, this PR can wait and ship as 5.0.0.
No feature flags in ldcli. To roll back, revert the commit and the generated commands return to the 2026-11-02 spec.
🤖 Generated with Claude Code
Note
Overview
Regenerates CLI resources from the latest production OpenAPI spec, exposing beta command groups for flag release plans and environment release plans (including default-plan get/set/clear), and adds segment scheduled change list/get/create/update/delete commands.
The deprecated
release-policies-betacommand group is removed to match the spec. Existingenvironment-releases-betabehavior is unchanged aside from doc tweaks;agent-control list-agent-skillsgains--sort,audit-log create-entriesgains--rollup, and several operation help texts are refreshed (experiments assignment sources, flag lifecycle deprecate/restore rules, integrations scope notes, segment docs).resource_utils.gomaps default environment release plan operations toset-defaultandclear-defaultsubcommands.Reviewed by Cursor Bugbot for commit 178d587. Bugbot is set up for automated code reviews on this repo. Configure here.
Related Jira issue: EMSR-2795: Release ldcli version with flag-release-plans-beta commands (generated from openapi)