build(deps): bump react-router-dom from 6.30.2 to 7.13.1#3
Closed
dependabot[bot] wants to merge 1 commit into
Closed
build(deps): bump react-router-dom from 6.30.2 to 7.13.1#3dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Bumps [react-router-dom](https://github.com/remix-run/react-router/tree/HEAD/packages/react-router-dom) from 6.30.2 to 7.13.1. - [Release notes](https://github.com/remix-run/react-router/releases) - [Changelog](https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/CHANGELOG.md) - [Commits](https://github.com/remix-run/react-router/commits/react-router-dom@7.13.1/packages/react-router-dom) --- updated-dependencies: - dependency-name: react-router-dom dependency-version: 7.13.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/react-router-dom-7.13.1
branch
from
0909334 to
7b65fb7
Compare
Contributor
Author
|
Superseded by #6. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/react-router-dom-7.13.1
branch
7 tasks
adm01-debug
added a commit
that referenced
this pull request
May 8, 2026
Validacao cruzada plano-vs-repo executada em 08/05/2026. Metricas Fase 0 corrigidas: - TS/TSX files: 1.671 -> 1.632 - Linhas de codigo: ~281k -> ~183k (gap nao-investigado de ~98k) - Edge functions: 87 -> 81 (F1-6.6 removeu 6) - Paginas top-level: 75 -> 50 (12 documentadas + 13 nao-rastreadas) - Sub-paginas: 50 -> 49 - Migrations: 366 -> 368 (+2: passkey + public_token) Atualizacoes: - F1-6.13 e Anexo C 🟡-10: 26 mencoes -> 11 mencoes (caiu organicamente) - F1-4: total de rotas 102 -> 98 - Adicionada nota de discrepancia explicita na tabela de metricas - Adicionada secao F1-9 (Investigacao de gap de metricas) com 5 tarefas - Adicionada entry 1.6 no Changelog Validacoes confirmadas: - 11 commits citados existem no historico - Typecheck verde (0 erros) - F1-1, F1-3, F1-6, F1-7, F1-8: 100 porcento das remocoes confirmadas - ESLint baseline: 1.571 erros congelados (confere) - Decisoes F3 (#2, #3, #4, #5, #7): codigo presente conforme esperado Sem mudancas em codigo. Apenas documentacao.
This was referenced May 9, 2026
adm01-debug
added a commit
that referenced
this pull request
May 10, 2026
….x Onda C #3) ## Onda C #3 — fix tipado em src/lib/external-db/products.ts O arquivo `enrichProducts` (em products.ts) recebia records do bridge externo (`invokeBatchBridge`) e os armazenava como `Record<string, unknown>[]`. Toda iteração depois (`variantsRecords.forEach((variant) => ...)`, `imagesRecords.forEach((img) => ...)`) acessava propriedades que TS via como `unknown` — gerando 36 erros TS2322/TS2345 em cascata. ## Fix 1. **Tipos auxiliares** específicos no topo do arquivo: - `VariantRow`: id, product_id, sku, color_id, color_name, color_code, color_hex, stock_quantity, selected_thumbnail, images - `ImageRow`: product_id, variant_id, url_cdn, url_original, filename, image_type, is_primary, is_og_image, applies_to_color, display_order, supplier_code, alt_text, title_text - `SupplierRow`: id, name, code - `ColorVariationRow`: id, name, slug, group_id - `ColorGroupRow`: id, name, slug 2. **Trocas pontuais nos 5 arrays de records**: - `Record<string, unknown>[]` → `{Variant,Image,Supplier,ColorVariation,ColorGroup}Row[]` - `as unknown[]` → cast pra tipo específico - Cast errado `as ExternalProduct[]` em suppliers → `as SupplierRow[]` 3. **Limpeza de `as string` redundantes** em `colorVariationMap`/ `colorGroupMap` agora que os tipos são específicos. ## Resultado | Métrica | Antes | Depois | Delta | |---|---|---|---| | Total tsc errors | 960 | **924** | **-36 (-3.8%)** | | products.ts | 36 | **0** | **-100%** ✨ | ## Validação runtime 🟢 **Equivalente**. Os tipos das rows refletem o schema real do bridge (verifiquei contra o uso em `forEach`/`map` no mesmo arquivo). Cast puramente TS — JS gerado é idêntico. `r.data.records as VariantRow[]` não muda comportamento. ## Risk 🟢 **Baixo**. Mudança puramente de tipos: - Comportamento runtime equivalente (mesmos métodos/spreads) - Tipos específicos refletem campos efetivamente acessados no código - Nenhum caller externo precisa mudar ## Test plan - [x] tsc total: 960 → 924 (-36) - [x] products.ts: 36 → 0 (-100%) - [x] .tsc-baseline.json regenerado - [ ] CI verde - [ ] CodeRabbit OK
adm01-debug
added a commit
that referenced
this pull request
May 10, 2026
….x Onda C #3) (#126) ## Onda C #3 — fix tipado em src/lib/external-db/products.ts O arquivo `enrichProducts` (em products.ts) recebia records do bridge externo (`invokeBatchBridge`) e os armazenava como `Record<string, unknown>[]`. Toda iteração depois (`variantsRecords.forEach((variant) => ...)`, `imagesRecords.forEach((img) => ...)`) acessava propriedades que TS via como `unknown` — gerando 36 erros TS2322/TS2345 em cascata. ## Fix 1. **Tipos auxiliares** específicos no topo do arquivo: - `VariantRow`: id, product_id, sku, color_id, color_name, color_code, color_hex, stock_quantity, selected_thumbnail, images - `ImageRow`: product_id, variant_id, url_cdn, url_original, filename, image_type, is_primary, is_og_image, applies_to_color, display_order, supplier_code, alt_text, title_text - `SupplierRow`: id, name, code - `ColorVariationRow`: id, name, slug, group_id - `ColorGroupRow`: id, name, slug 2. **Trocas pontuais nos 5 arrays de records**: - `Record<string, unknown>[]` → `{Variant,Image,Supplier,ColorVariation,ColorGroup}Row[]` - `as unknown[]` → cast pra tipo específico - Cast errado `as ExternalProduct[]` em suppliers → `as SupplierRow[]` 3. **Limpeza de `as string` redundantes** em `colorVariationMap`/ `colorGroupMap` agora que os tipos são específicos. ## Resultado | Métrica | Antes | Depois | Delta | |---|---|---|---| | Total tsc errors | 960 | **924** | **-36 (-3.8%)** | | products.ts | 36 | **0** | **-100%** ✨ | ## Validação runtime 🟢 **Equivalente**. Os tipos das rows refletem o schema real do bridge (verifiquei contra o uso em `forEach`/`map` no mesmo arquivo). Cast puramente TS — JS gerado é idêntico. `r.data.records as VariantRow[]` não muda comportamento. ## Risk 🟢 **Baixo**. Mudança puramente de tipos: - Comportamento runtime equivalente (mesmos métodos/spreads) - Tipos específicos refletem campos efetivamente acessados no código - Nenhum caller externo precisa mudar ## Test plan - [x] tsc total: 960 → 924 (-36) - [x] products.ts: 36 → 0 (-100%) - [x] .tsc-baseline.json regenerado - [ ] CI verde - [ ] CodeRabbit OK
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.
Bumps react-router-dom from 6.30.2 to 7.13.1.
Release notes
Sourced from react-router-dom's releases.
Changelog
Sourced from react-router-dom's changelog.
... (truncated)
Commits
aa3f078chore: Update version for release (#14829)3207a5cchore: Update version for release (pre) (#14814)5557ba3chore: Update version for release (#14749)62c6e0echore: Update version for release (pre) (#14738)26653a6chore: Update version for release (#14712)7ac2346chore: Update version for release (pre) (#14709)b34a9cdchore: Update version for release (#14668)48b1be4chore: Update version for release (pre) (#14662)ff50507Update monorepo internal React deps (#14639)c257ee1feat(rsc): add support for custom entry files in RSC Framework Mode (#14643)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)