| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
feat(api): get environment API keys by UUID (#7352) Adds `GET /environments/:environmentUuid/api-keys/:keyUuid`. - Introduces the `account:environments:api_keys:read` scope. - Returns an environment API key’s metadata and decrypted secret. - Adds a shared service method for UUID lookups that decrypts secrets. - Documents the endpoint in OpenAPI, HTTP API docs, and LLM docs. - Adds integration coverage for authentication, scopes, filtering, validation, wildcard access, and isolation. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7352?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 4 小时前 | |
docs: fix heading hierarchy on core and integration pages (#7201) Final part of the heading work from #7194 (convention) and #7197 (mechanical sweep). These are the pages that needed judgment rather than a mechanical demotion, so this PR is small enough to read line by line. Independent of #7197 — no file overlap, so the two can merge in either order. ## Core reference and guides `frontend-sdk.mdx` and the three `migrations/*.mdx` guides had multiple body H1s with real sub-sections underneath. Demoted the H1s **and their children**, so the nesting stays intact: ``` ## Migration steps (was #) ### Step 1: ... (was ##) ### Step 2: ... (was ##) ## Related guides unchanged - a top-level sibling, not a migration step ``` This also fixes an inconsistency upstream introduced in `migrate-from-public-key.mdx`, where `### Step 3: Clean up` sat a level below its `## Step 1` / `## Step 2` siblings. All three now sit at H3. ## Two headings deleted, not demoted Per the convention: a heading that only restates its page `title` gets deleted. - `api-keys.mdx` — `# API keys` on a page titled "API keys" - `roller.mdx` — `# Roller API` on a page titled "Roller" Every other integration main page (`auth0-cc`, `gong`, `coda`, …) goes straight from the snippet imports to its first real section, so Roller now matches the rest. ## One heading renamed `google-security-review.mdx` — `# Recommended process` → `## Process overview`. It summarises the steps 1–5 that follow it, so the old name read like a container for them. Worth noting what I deliberately **didn't** do: nesting those steps under it would have pushed 13 sub-sections (`Demo video`, `Scope justifications`, `Privacy policy`, …) from H3 to H4 and out of Mintlify's table of contents. The flat outline is better for a page this long, so only the name changed. ## Eight integration pages: sibling step levels `maximizer`, `youcanbook-me`, `codeclimate`, `loop-returns`, `oracle-hcm`, `roam-scim`, `instantly`, `datto-rmm-password-grant`. Each had `Step N` headings at mixed levels, so some steps rendered as sub-sections of the previous step (e.g. `## Step 1` followed by `#### Step 2`). Now consistent within each page. Level-only edits, so anchors are untouched. ## Anchor impact Verified by diffing the set of heading **texts** per file, since anchors derive from text rather than level. Exactly three anchors move: | Page | Anchor | Inbound links | |---|---|---| | `api-keys.mdx` | `#api-keys` removed | none | | `roller.mdx` | `#roller-api` removed | none | | `google-security-review.mdx` | `#recommended-process` → `#process-overview` | none | Every other change is level-only, so those anchors resolve exactly as before. The anchors that *are* linked on `api-keys.mdx` (`#scopes`, `#environment-api-keys`, `#account-api-keys`) all still exist. ## Verification - `mintlify broken-links` → `success no broken links found` - Every changed line in the `.mdx` files is a heading — no content edits - `llms-full.txt` regenerated with `npm run docs:generate:llms`; its diff is heading lines only, and `llms.txt` / `api-catalog.txt` are unchanged - With #7197, no body H1 remains anywhere in `docs/**/*.mdx` ## Found along the way, deliberately not fixed here **13 broken anchor links** (8 unique targets) already on master. `mintlify broken-links` does not validate fragments, so these pass CI today: ``` /reference/backend/http-api/api-keys#cicd-deploy <- guides/functions/ci-cd.mdx (heading generates #ci-cd-deploy) /guides/auth/auth-guide#generate-session-token <- guides/auth/mcp-auth.mdx /guides/auth/auth-guide#trigger-auth-flow <- guides/auth/mcp-auth.mdx /guides/auth/auth-guide#save-connection-id-from-webhook <- guides/auth/mcp-auth.mdx /guides/auth/auth-guide#re-authorize-an-existing-connection <- guides/auth/token-refreshing.mdx /api-integrations/github-app#setup-guide <- .../how-to-register-your-own-github-app-api-oauth-app.mdx /reference/backend/backend-sdk/node#start-schedule-for-syncs <- guides/functions/syncs/sync-functions.mdx /reference/backend/backend-sdk/node#trigger-syncs <- guides/functions/syncs/sync-functions.mdx ``` None are caused by this PR. Each needs a per-case call (fix the link, or restore the heading it used to point at), so they belong in their own PR rather than riding along here. **3 duplicate step numbers** — `drupal`, `keeper-scim` and `kintone-user-api` connect guides each number a step twice (e.g. 1, 2, 2). Fixing those changes heading text and therefore anchors, so it is a content fix rather than a hierarchy one. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7201?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 18 天前 | |
feat(cli): support mtls (#7325) ## Summary - Let the CLI present a client certificate when talking to a self-hosted Nango API behind mTLS, so customers no longer have to disable mTLS for `deploy` / `dryrun` / `pull`. - Configure it with `NANGO_CLI_TLS_CERT` (path to a PEM). A file that contains both cert and key is enough; `NANGO_CLI_TLS_KEY` / `NANGO_CLI_TLS_CA` cover split files and a private CA. - The same TLS agent is used on every CLI-to-API path (axios, fetch, and the Node SDK). Invalid cert/key pairs fail at load time. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7325?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> | 7 天前 |