| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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 | 3 个月前 | |
chore(eslint): manual pass over some folders (#3979) ## Changes Didn't want a big PR for import order but it's definitely not going to end without a big push - Import order: manual pass over some folder <!-- This is an auto-generated description by mrge. --> --- ## Summary by mrge Reordered and cleaned up import statements across multiple files to improve code consistency and follow ESLint rules. No functional changes were made. <!-- End of auto-generated description by mrge. --> | 1 年前 | |
feat(fleet): add support for runner replicas (#5579) Allow runner instances to have more than one replicas Warning: requires runner to be updated to use shared kvstore for conflict detection before we can make a runner instance have more than one replica <!-- Summary by @propel-code-bot --> --- This change also extends fleet configuration to support replica counts via shared types, database schemas, and model mappings, and updates providers and supervisor logic so replica overrides are treated as configuration differences and applied when creating or updating nodes. <details> <summary><strong>Key Changes</strong></summary> • Added `replicas` columns via migration in `packages/fleet/lib/db/migrations/20260305000000_add_replicas.ts` for `nodes` and `node_config_overrides` • Extended `NodeConfig`, `Node`, and `NodeConfigOverride` types with `replicas` in `packages/types/lib/fleet/index.ts` and `packages/fleet/lib/types.ts` • Propagated `replicas` through model mappings and creation paths in `packages/fleet/lib/models/nodes.ts` and `packages/fleet/lib/models/node_config_overrides.ts` • Updated supervisor logic in `packages/fleet/lib/supervisor/supervisor.ts` to outdate nodes on replica changes and apply replica overrides when creating nodes • Adjusted runner providers to default `replicas: 1` and use replica counts in `packages/jobs/lib/runner/kubernetes.ts` plus conflict mode env var when `replicas > 1` </details> <details> <summary><strong>Possible Issues</strong></summary> • Replica override application uses `||` fallback in `packages/fleet/lib/supervisor/supervisor.ts`, which could treat `0` as falsy if ever allowed for `replicas` </details> --- *This summary was automatically generated by @propel-code-bot* | 6 个月前 | |
chore(fleet): remove deployment commit_id column (#3451) deployments.commit_id column is not being used anymore. Depends on https://github.com/NangoHQ/nango/pull/3450 and setting non overriden values to `NULL` in `node_config_overrides` | 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 | 3 个月前 | |
fix(fleet): fix node config override checks (#5630) <!-- 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 --> --- **Fix node config override comparisons and persistence** This PR updates fleet node config override handling to include `executionTimeoutSecs` and `provisionedConcurrency` in outdated-node detection and in override upsert updates. The changes ensure these override fields are compared explicitly and persisted when overrides change. --- *This summary was automatically generated by @propel-code-bot* | 6 个月前 | |
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 | 3 个月前 | |
feat(fleet): add support for runner replicas (#5579) Allow runner instances to have more than one replicas Warning: requires runner to be updated to use shared kvstore for conflict detection before we can make a runner instance have more than one replica <!-- Summary by @propel-code-bot --> --- This change also extends fleet configuration to support replica counts via shared types, database schemas, and model mappings, and updates providers and supervisor logic so replica overrides are treated as configuration differences and applied when creating or updating nodes. <details> <summary><strong>Key Changes</strong></summary> • Added `replicas` columns via migration in `packages/fleet/lib/db/migrations/20260305000000_add_replicas.ts` for `nodes` and `node_config_overrides` • Extended `NodeConfig`, `Node`, and `NodeConfigOverride` types with `replicas` in `packages/types/lib/fleet/index.ts` and `packages/fleet/lib/types.ts` • Propagated `replicas` through model mappings and creation paths in `packages/fleet/lib/models/nodes.ts` and `packages/fleet/lib/models/node_config_overrides.ts` • Updated supervisor logic in `packages/fleet/lib/supervisor/supervisor.ts` to outdate nodes on replica changes and apply replica overrides when creating nodes • Adjusted runner providers to default `replicas: 1` and use replica counts in `packages/jobs/lib/runner/kubernetes.ts` plus conflict mode env var when `replicas > 1` </details> <details> <summary><strong>Possible Issues</strong></summary> • Replica override application uses `||` fallback in `packages/fleet/lib/supervisor/supervisor.ts`, which could treat `0` as falsy if ever allowed for `replicas` </details> --- *This summary was automatically generated by @propel-code-bot* | 6 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 3 个月前 | ||
| 1 年前 | ||
| 6 个月前 | ||
| 1 年前 | ||
| 3 个月前 | ||
| 6 个月前 | ||
| 3 个月前 | ||
| 6 个月前 |