Repository navigation
chore(coverage): sync manifest to n8n 2.46.4 - #40
Merged
Merged
Conversation
Upstream Public API spec n8n 2.46.4 (API 1.1.1) adds dependency lookups and promotion environments, and drops /promotions/connections. - Add 16 operations as planned, upstream-only: phase 34 (dependencies), phase 35 (promotion environments), phase 36 (environment apply/promote). - Mark the 16 /promotions/connections operations retired. Commands stay; older instances still serve them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5 tasks done
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.
What / why
Syncs
internal/coverage/manifest.jsonto the stable upstream n8n Public API spec n8n 2.46.4 (API 1.1.1;openapi.upstream.ymlsha256f33305801effecf2c5c1137c138e628f8e0147761d621d741f674030e3c7ccef). This PR changes only the manifest. It adds no commands or client code. It unblocks the PRs that will implement the new ops.Changes
Added: 16 ops,
status: planned,availability: upstream-only, new phases 34–36. Scopes come fromx-required-scope.GET /workflows/{workflowId}/dependencies(getWorkflowDependencies,workflow:read)GET /credentials/{credentialId}/dependencies(getCredentialDependencies,credential:read)GET /data-tables/{dataTableId}/dependencies(getDataTableDependencies,dataTable:read)Promotions):GET/POST /promotions/environmentsGET/PUT/DELETE /promotions/environments/{promotionEnvironmentId}POST .../connect,POST .../disconnect(gitConnection:clone)GET .../projectsPOST/DELETE .../projects/{projectId}(gitConnection:manageProjects)POST .../apply,POST .../apply/continue(gitConnection:pull)POST .../promote(gitConnection:push)Retired: all 16
/promotions/connections...ops (phase 29, plusapply/continuefrom phase 31). Their availability changes frombothtoretired. Their status and commands stay the same, because older instances still serve them.deliveredThroughstays at 33. No test or help text changed, somake docswas not needed.Verification
go test ./internal/coverage/...with the 2.46.4 spec present: ok.TestManifestMatchesSpecpasses, and before this change it failed with 16 removed and 16 added ops.make check: green (lint,go test -race ./..., cross-builds,go mod tidy -diff, govulncheck).make checkpasses locallymake docsrun if CLI help changed (not needed: no help change)No secrets/keys/tokens in diff or logs
No
v*tag or release commit in this PR (maintainer releases separately)Notes for reviewer
openapi.yml) because I don't have it, soTestAvailabilityMatchesSpecswas skipped. The new ops are markedupstream-onlybecause only the upstream document is known to declare them. Once the target spec is fetched, that test will flag any availability that needs to change, including the retired connections if the target still serves them, in which case they would becometarget-only.applyPackage,continueApplyPackage,promotePackageanddisconnectPromotionCheckoutfrom the retired connection ops. That's fine because the key is method plus path.🤖 Generated with Claude Code