Repository navigation
chore(deps): bump baseline-browser-mapping from 2.10.42 to 2.11.22 in /app - #149
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping) from 2.10.42 to 2.11.22. - [Release notes](https://github.com/web-platform-dx/baseline-browser-mapping/releases) - [Commits](web-platform-dx/baseline-browser-mapping@v2.10.42...v2.11.22) --- updated-dependencies: - dependency-name: baseline-browser-mapping dependency-version: 2.11.22 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
roger-guifav
left a comment
There was a problem hiding this comment.
TL;DR
Atualizacao de uma base de dados de compatibilidade de navegadores (baseline-browser-mapping), da versao 2.10.42 para 2.11.22. E so dado usado no build do front — nao muda codigo do app. Instalacao, verificacao de tipos e testes passaram. Seguro para merge.
Verdict: Approve
(revisado no head SHA 098c0e1)
Parecer
Bump do baseline-browser-mapping em /app, aberto pelo bot de dependencias. O pacote e uma tabela de mapeamento de features web para navegadores, consumida pela browserslist em tempo de build; o diff e apenas no lockfile, conferido contra a API. O salto de versao (varias revisoes de dados de uma vez) e normal para esse tipo de pacote, que versiona dados e nao API. Validacao local completa verde. Ha outros tres PRs de bump que tocam o mesmo lockfile; apos o primeiro merge, os demais sao rebaseados pelo proprio bot. Pergunta de merge: mergearia e dormiria tranquilo — sim.
Criticos (P0)
nenhum
Bloqueadores de correcao (P1)
nenhum
Enderecar no PR (P2)
nenhum
Enderecar no PR (P3 / nits)
nenhum
Acoes que somente o humano pode fazer (ainda...)
nenhuma alem do merge
Verificado
- diff contra a main fresca toca apenas o lockfile do app; contagem confere com a API
- npm ci ok; prisma generate ok
- tsc --noEmit: 0 erros
- vitest: 680 testes passaram, 8 skipped, 0 falhas
Roger (Hermes KVM) - review v2 - 098c0e1
Bumps baseline-browser-mapping from 2.10.42 to 2.11.22.
Release notes
Sourced from baseline-browser-mapping's releases.
Commits
af7c3c4Patch to 2.11.22 because browser or feature data changed7e10cadBrowser or feature data changedebb9702Updating static siteecc57a3Updating static site0e5ed80Patch to 2.11.21 because browser or feature data changed11da0b6Browser or feature data changed69fcc81Updating static siteb964de0Patch to 2.11.20 because browser or feature data changed723099fBrowser or feature data changedf44163dUpdating static siteDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.