| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(cli): compile one file and symlink (#3905) | 1 年前 | |
chore(lint): move import sorting to Prettier (#6582) ## Problem We're replacing ESLint with oxlint (NAN-5769). oxlint has no `import/order` equivalent — its maintainers deliberately defer import sorting to the formatter — so import ordering needs a new home before the linter swap. ## Solution Move import ordering to Prettier via `@ianvs/prettier-plugin-sort-imports`, configured to replicate the existing `import/order` grouping exactly: builtins → external → `@nangohq/*` → `@/*` + relative → type imports, blank lines between groups, alphabetised within. The `import/order` rule (and its now-pointless migrations override) is removed from the ESLint config. Doing this first — while ESLint still runs — means the change is verifiable in isolation: format-on-save behaviour is identical for developers, and CI's existing `prettier --check` + ESLint both still gate it. Two commits: - `chore(lint): move import sorting to Prettier` — the plugin + config (this is the one to actually review) - `style: sort imports across the codebase` — the mechanical 489-file reformat (skim only; import order changes only, no logic) Part of NAN-5769. Sub-issue: NAN-5808. ## Testing - `eslint . --quiet` passes clean (exit 0) on the reformatted code - Reformat is purely mechanical — only import grouping/order changed - Spot-checked plugin output against the old `import/order` grouping; identical | 2 个月前 | |
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> | 5 天前 | |
feat(cli): Clear mocks in generated sync tests (#5605) <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Improve generated sync test template mock isolation** Updates the sync test template to create a fresh `NangoSyncMock` per test, add `afterEach` cleanup for `vitest` mocks, and add clearer spy normalization for batch save/delete comparisons. Adjusts unit test expectations in `packages/cli/lib/services/test.service.unit.cli-test.ts` to match the new template output. --- *This summary was automatically generated by @propel-code-bot* | 5 个月前 | |
fix: vitest upgrade (#6315) <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> | 3 个月前 | |
feat(cli): zero yaml compile (#4116) ## Changes Contributes to https://linear.app/nango/issue/NAN-3242/new-compilation-and-deploy - CLI zero yaml compile Add full compilation for zero yaml. It's only to compile all, no support for nango dev yet. The files are split from the rest to avoid bloating the current services. - Typechecking: runs typescript checker, nothing crazy - Bundling: use esbuild to bundle files and imported files - Rebuild: virtual nango.yaml for deployment and dryrun later - Added missing types for Metadata - Added support for void and never - Clean up legacy code ## 🧪 Tests I don't yet provide an easy way for you to test, there are the fixtures for the test that's basically it but its missing the package.json, so if you are motivated you can add a package.json with nango and zod and run compile. The unit tests and snapshots are showing the expected output.  <!-- Summary by @propel-code-bot --> --- **feat(cli): Add Zero-Yaml Compilation Pipeline for Nango CLI** This major PR implements end-to-end CLI support for compiling 'zero-yaml' integration projects, enabling TypeScript-based integrations to be typechecked, bundled, and compiled without a nango.yaml file. Major new modules include an entry scanning/typecheck/build pipeline (with esbuild and custom Babel plugin), robust output post-processing, and definition/model reconstruction for deploy and validation, along with improved Nango type support (including void and never), upgrades to dependencies for esbuild/Babel, and comprehensive new unit/snapshot tests. Existing CLI entrypoints, pre-check, and error handling are refactored to route zero-yaml projects to the new pipeline while maintaining backward compatibility for legacy (yaml-based) projects. **Key Changes:** • Introduces zero-yaml compile workflow: `TypeScript` typechecking, esbuild bundling with Babel plugin, virtual nango.yaml reconstruction • Adds ``CLI`` detection and pipeline segregation for zero-yaml vs. yaml-based projects • Implements robust type/model parsing, including void/never and enhanced union/array/optional handling • Removes legacy and unused code (e.g., `isJsOrTsType`) • Refactors ``CLI`` compile command and error handling for improved clarity • Significant test additions: unit, fixtures, and snapshots for the new compile pipeline • Upgrades key dependencies (esbuild, babel, zod, types) and adds missing dev dependencies **Affected Areas:** • ``CLI`` zero-yaml compile pipeline (`zeroYaml`/compile.ts, `zeroYaml`/definitions.ts, `zeroYaml`/`zodToNango`.ts) • ``CLI`` command and entrypoint handling (index.ts) • Model and definition helpers/services • Test fixtures and helpers • runner-sdk typing for metadata/void/never • Package and dependency management **Potential Impact:** **Functionality**: Enables compiling/deploying zero-yaml projects, i.e. projects with entrypoint index.ts and no nango.yaml; introduces new error and handling logic for TypeScript-based integrations; legacy yaml integrations remain unaffected. **Performance**: esbuild/Babel pipeline may introduce additional build time for large projects but is only used in zero-yaml path; isolated from legacy workflow. **Security**: No direct security impact; code only produces intermediate deployment bundles and metadata, does not affect runtime execution or secrets. **Scalability**: Pipeline is modular and can handle multiple entrypoints and larger projects; design anticipates future dev server and further CLI tooling extensions. **Review Focus:** • Zero-yaml compile flow: correctness of entrypoint detection, typechecking, esbuild/Babel transpilation, and output structure • Type/model extraction and edge case handling in `zodToNango`.ts (void, never, optionals, unions/arrays, references) • Definition/model reconstruction logic (definitions.ts) and its robustness for deployment cycle • Dependency upgrade risks-especially with esbuild/Babel integration and cross-version compatibility • Modularization of compile steps and maintainability of `compileAll`/related functions <details> <summary><strong>Testing Needed</strong></summary> • Validate compile command on real-world zero-yaml projects (index.ts with syncs/actions/on-event scripts) • Review expected output for various `TypeScript` constructs (esp. with void/never/optionals/unions) • Manually test error paths for missing dependencies, export errors, or misconfigured project structures • Ensure backward compatibility by testing yaml-based project compilation and deploy • Inspect produced output (snapshot/unit tests, .nango folder, generated ``JSON``/``TS`` schemas) for correctness </details> <details> <summary><strong>Code Quality Assessment</strong></summary> **test coverage (unit, fixtures, snapshots)**: Thorough-covers key cases and new flows; easy to follow and extend. **packages/cli/lib/index.ts**: Clean routing for zero-yaml vs. yaml flows; improved error handling. **package.json/dependencies**: Properly updated and explicit; superfluous dev deps removed. **packages/cli/lib/zeroYaml/compile.ts**: Well-structured, logical phase separation (typecheck, bundle, rebuild, etc.), but compileAll remains large; good inline comments and error reporting. Suggest future further modularization. **packages/cli/lib/zeroYaml/definitions.ts**: Clear and modular; robust error-checking and type validation; legacy terminology ('Parsed') noted. **packages/cli/lib/zeroYaml/zodToNango.ts**: Comprehensive type guard coverage and readable conversions; accommodates difficult zod schema cases. </details> <details> <summary><strong>Best Practices</strong></summary> **Typescript**: • Strict compiler options and type safety • Full union/void/never/optional/array coverage **Testing**: • New unit, integration, and snapshot tests for zero-yaml pipeline • Good fixture design **Dependency Management**: • Explicit upgrades and types • Removes dead code/deps **Modularity**: • Compile pipeline segmented by phase, but could further improve function-level decomposition </details> <details> <summary><strong>Possible Issues</strong></summary> • Use of legacy internal terms like 'Parsed' and 'Definitions' may cause confusion and merit future refactor • Custom Babel transformation for create wrappers could be brittle-edge cases need ongoing monitoring as APIs evolve • Partial error messaging for missing deps/misconfigurations; improvement for onboarding may be required • Potential for esbuild/Babel config drift; futureproofing needs tight version locking/testing • nango.json output purpose is unclear and not thoroughly documented; clarify or document before wide adoption </details> --- *This summary was automatically generated by @propel-code-bot* | 1 年前 | |
fix(cli,dashboard): resolve symlinked integrations in pull and github links (#6632) The `nango pull` and `nango clone` commands would fail for symlinked integrations. Links to code in github would also be incorrect. This PR fixes that by: - Using the metadata already available in `flows.zero.yaml` to resolve symlinks server-side. - Doing a pre-fetch in github to check for symlinks in the CLI (it doesn't have access to the metadata, so we need to fetch). I did not try to over-optimize this, so the CLI does an extra call to github to see if it's a symlink. Keeps the diff way shorter. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6632?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. --> | 2 个月前 | |
fix(cli): stop compile test hanging on npm audit (#7396) ## Problem `compile.unit.cli-test.ts > should compile a minimal integration` times out at 20s and fails `npm run test:cli` on unrelated PRs — [this run](https://github.com/NangoHQ/nango/actions/runs/33847751619/job/100949848121?pr=7395), plus the #7391 merge-queue run and several other branches. The test shells out to a real `npm i`. npm's audit step POSTs to the registry and can leave that socket open after the install itself has finished, so the child process never exits. It reproduces on every local run but only intermittently in CI, which is why the test has been flaking rather than failing outright. ## Solution - Pass `--no-audit --no-fund` to the `npm i` the test runs, so the child exits when the install does. ## Testing Plain `npm i` hung on all five local attempts (up to a 300s timeout); `--no-audit` passed on all three; `--no-fund` alone still hung. The file now passes 30/30 in ~3s. | 3 天前 | |
feat(cli): drop `nango.yaml` support in CLI commands (#5604) Removes `nango.yaml` ramifications and validates for zero-yaml in all relevant commands. Deletes now unused code (might have missed some spots, but I will likely find more as I continue this) Also minor renaming of a couple functions. <!-- Summary by @propel-code-bot --> --- It also routes all key CLI commands through zero‑yaml validation and compilation, simplifies dryrun to rely solely on zero‑yaml definitions, removes remaining legacy/hidden CLI workflows tied to nango.yaml, and tweaks initialization behavior to focus on zero‑yaml projects. --- *This summary was automatically generated by @propel-code-bot* | 5 个月前 | |
fix(cli): Remove directory requirement in verification service (#3417) <!-- Describe the problem and your solution --> Mentioned by Samuel. Also adds output of the init directory: <img width="912" alt="image" src="https://github.com/user-attachments/assets/bf733a50-2caf-48ff-86f3-810b959b0062" /> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> | 1 年前 | |
feat: return CLI exit codes for remote functions (#6025) <!-- Describe the problem and your solution --> Adds explicit CLI exit codes for compile, dryrun, and deploy failures so remote-functions can classify E2B/Docker command failures from exit codes instead of output regexes. Dryrun service methods now return Result values, and remote/local dryrun and deploy clients use CLI exit-code mapping while preserving stdout-only success parsing. <!-- Issue ticket number and link (if applicable) --> NAN-5373 <!-- Testing instructions (skip if just adding/editing providers) --> - npm run test:unit -- packages/cli/lib/utils.unit.test.ts packages/cli/lib/services/dryrun.service.unit.test.ts packages/cli/lib/services/sdk.service.unit.test.ts packages/server/lib/services/remote-function/command-output.unit.test.ts packages/server/lib/services/remote-function/cli-exit-codes.unit.test.ts packages/server/lib/services/remote-function/dryrun-client.unit.test.ts packages/server/lib/services/remote-function/deploy-client.unit.test.ts - npm run ts-build | 3 个月前 | |
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> | 5 天前 | |
Gh #1250 unified and yaml updates (#1266) * [server] add new endpoint (`GET /api/:model`) to serve records Serving records can now be done via the `GET /api/:model` endpoint. Example: `GET /api/GithubIssue` The same parameters than `sync/records` are supported (delta, offset, ...) * model rest api: support kebab-case path (ex: /api/github-issue) model in path is transformed fromm kebab-case to capitalized camel case * REST API for action: add /in/:action_name Triggering actions can now be done with the /in/:action_name endpoint This route supports different HTTP methods The appropriate HTTP methods for a given action is defined in the sync_config table (metadata column) For now this metadata.method is not set and the method therefore default to POST * model records and actions are exposed behind an unified api endpoint /v1/:category/:action_or_model The only supported category is 'all' for now * add 'endpoints' field to nango.yaml 'endpoints' field allow user to specify the endpoint path to access a model or trigger an action * add: generate OpenAPI spec for all endpoints currently the function returns a spec for all endpoints for a given environment * [gh-#1250] endpoint logic small tweaks * [gh-#1250] migrate templates to use paginate * [gh-#1250] move templates * [gh-#1250] remove unused migration template file * [gh-#1250] update npm command for moved templates * [gh-#1250] move nango.yaml to a template directory * [gh-#1250] convert config object works for v1 and v2 and cli refactor / organization * [gh-#1250] refactor and cli reorg * [gh-#1250] json schema validation of v1 and v2 * [gh-#1250] better error handling and more robust tests * [gh-#1250] schema and error handling improvements * [gh-#1250] fix model output * [gh-#1250] use v2 object * [gh-#1250] fix tests * [gh-#1250] remove unused error * [gh-#1250] fix template to be v2 version and use config object when generating * [gh-#1250] remove unused types * [gh-#1250] json schema nice messages and ignore irrelevant ones * [gh-#1250] better json schema validation logic * [gh-#1250] fix test * [gh-#1250] drop the v1 for getSyncConfig --------- Co-authored-by: Thomas Bonnin <233326+TBonnin@users.noreply.github.com> | 2 年前 | |
feat(custom-validation-script): spec custom verification endpoints as a on events script (#4609) <!-- Describe the problem and your solution --> Add in a `validate-connection` on-event script that kicks off right after the connection is saved. If an error is thrown during the script then the connection errors out and is silently deleted and an auth error is returned during the auth process. <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- Summary by @propel-code-bot --> --- **Support 'validate-connection' Event Script for Custom Connection Validation** This PR introduces a new 'validate-connection' event script mechanism within the Nango platform. Integration developers can now define one or more scripts to run immediately after a connection is created, allowing for custom, programmatic validation of the newly established connection/credentials. If any 'validate-connection' script throws an error, the connection is considered invalid, a dedicated 'connection_validation_failed' error is returned (including surfaced failure details), and-if applicable-the connection is hard-deleted with no trace. The feature is implemented consistently across all supported auth modes (API Key, OAuth, Basic, JWT, Signature, App Store, Unauthenticated, Two-Step, TBA), and includes changes to backend controllers, configuration schema, developer experience, logs, error handling, docs, type system, migration logic, CLI/config validation, and UI surfaces. <details> <summary><strong>Key Changes</strong></summary> • Added support for `validate-connection` as an on-event script across all connection auth flows. • Validation scripts run synchronously post-connection creation; errors abort creation and may trigger a hard-delete. • Dedicated ``connection_validation_failed`` error response surfaced to ``API`` clients and displayed in developer logs/``UI``. • Backend controller refactors to inject validate-connection logic into all auth endpoints, with precise sequencing relative to connection insertion and error handling semantics. • Schema, `TypeScript`, and ``CLI``/schema tooling extended for the new event trigger, including migration for ``DB`` enum ``script_trigger_event``. • Documentation and code comment updates across ``YAML``/``JSON`` schema, developer docs, and code-level references. • Developer Connect ``UI`` updated to correctly surface custom validation error messages in the user interface. • Expanded integration and parser tests to accommodate the new trigger type and related config expansions. </details> <details> <summary><strong>Affected Areas</strong></summary> • Authentication backend controllers for all credential modes • On-event script management services, orchestrator, and execution paths • Configuration file parsing, ``CLI``, ``YAML``/``JSON`` schema definitions • Database: enumeration and on-event script migration (type addition) • Error handling, logging, and user-facing operation logs/``UI`` • Integration script `SDKs`/types and documentation • Integration test suites and config snapshots </details> --- *This summary was automatically generated by @propel-code-bot* | 11 个月前 | |
fix(function): align types between types package and runner-sdk (#6964) This commit consolidates and align the types between `runner-sdk` and the `types` packages <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6964?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. --> | 1 个月前 | |
feat: add CreateFunction definition (#6664) Also remove the recent changes made around createWebhook. They will be folded and reintroduced as part of the function primitive initiative `function` definition types are in https://github.com/NangoHQ/nango/pull/6664/changes#diff-cedceb6eb8af423d2de17f68fed59bd218cf3c5029655359b4361d444c733256 The rest is reverting support for `createWebhook` in `runner-sdk` and `cli` <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6664?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. --> | 2 个月前 | |
feat(telemetry): implement CLI usage tracking (#6691) - Added telemetry support for CLI commands to track usage events. - Introduced device ID generation and storage for anonymous tracking. - Updated CLI options to enable/disable telemetry. - Created a new endpoint for receiving telemetry data on the server. - Enhanced headers in HTTP requests to include device ID for tracking. This change aims to improve insights into CLI usage patterns while respecting user privacy preferences. <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6691?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. --> | 1 个月前 | |
feat(cli): drop `nango.yaml` support in CLI commands (#5604) Removes `nango.yaml` ramifications and validates for zero-yaml in all relevant commands. Deletes now unused code (might have missed some spots, but I will likely find more as I continue this) Also minor renaming of a couple functions. <!-- Summary by @propel-code-bot --> --- It also routes all key CLI commands through zero‑yaml validation and compilation, simplifies dryrun to rely solely on zero‑yaml definitions, removes remaining legacy/hidden CLI workflows tied to nango.yaml, and tweaks initialization behavior to focus on zero‑yaml projects. --- *This summary was automatically generated by @propel-code-bot* | 5 个月前 | |
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> | 5 天前 | |
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> | 5 天前 | |
feat(telemetry): implement CLI usage tracking (#6691) - Added telemetry support for CLI commands to track usage events. - Introduced device ID generation and storage for anonymous tracking. - Updated CLI options to enable/disable telemetry. - Created a new endpoint for receiving telemetry data on the server. - Enhanced headers in HTTP requests to include device ID for tracking. This change aims to improve insights into CLI usage patterns while respecting user privacy preferences. <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6691?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. --> | 1 个月前 | |
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> | 5 天前 | |
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> | 5 天前 | |
chore(release): 0.71.6 | 5 天前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 年前 | ||
| 2 个月前 | ||
| 5 天前 | ||
| 5 个月前 | ||
| 3 个月前 | ||
| 1 年前 | ||
| 2 个月前 | ||
| 3 天前 | ||
| 5 个月前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 5 天前 | ||
| 2 年前 | ||
| 11 个月前 | ||
| 1 个月前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 5 个月前 | ||
| 5 天前 | ||
| 5 天前 | ||
| 1 个月前 | ||
| 5 天前 | ||
| 5 天前 | ||
| 5 天前 |