chore: release 2.5.0 - #48
Merged
Merged
Conversation
Cinco PRs entraram na main depois da v2.4.0 sem que ninguem bumpasse a versao - entre eles a correcao de seguranca do fast-uri (#35) e toda a i18n. Como o workflow de release so dispara quando backend/package.json muda, nada disso foi publicado. Esta e a terceira vez que a versao fica para tras desse jeito. O bump em si esta aqui; o que impede a repeticao vem em PR separado.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prepares the v2.5.0 release by bumping the version in both backend and frontend packages (including their lockfiles) and adding a new 2.5.0 section to the changelog so the release workflow can publish the accumulated changes since v2.4.0.
Changes:
- Bump
incident-kb-backendandincident-kb-frontendversions from 2.4.0 to 2.5.0. - Update both
package-lock.jsonfiles to match the new version. - Add a
2.5.0entry toCHANGELOG.md(Segurança / Adicionado / Desempenho / Corrigido) and include the release link reference.
Reviewed changes
Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| frontend/package.json | Bumps frontend package version to 2.5.0. |
| frontend/package-lock.json | Updates frontend lockfile metadata to 2.5.0. |
| backend/package.json | Bumps backend package version to 2.5.0. |
| backend/package-lock.json | Updates backend lockfile metadata to 2.5.0. |
| CHANGELOG.md | Adds the 2.5.0 release notes section and release link reference. |
Files not reviewed (2)
- backend/package-lock.json: Generated file
- frontend/package-lock.json: Generated file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### Adicionado | ||
|
|
||
| - A API passou a responder as mensagens de erro no idioma do usuário. Das 255 |
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.
O problema (de novo)
Cinco PRs entraram na
maindepois da v2.4.0 e nenhum bumpou a versão:fast-uri(GHSA-7p8r-x3mc-p8w7, alta)Como o workflow de release só dispara quando
backend/package.jsonmuda, nadadisso foi publicado. O badge de release segue mostrando v2.4.0, e quem clonar
uma tag não recebe a correção de segurança.
É a terceira vez que a versão fica para trás desse jeito — aconteceu antes
da 2.3.0 e antes da 2.4.0.
Este PR
Bump para 2.5.0 (
npm version --no-git-tag-versionnos dois pacotes, para oslocks acompanharem) e a seção correspondente no
CHANGELOG.md, agrupando porSegurança / Adicionado / Desempenho / Corrigido.
Escolhi minor porque há funcionalidade nova (i18n da API e das telas), não
só correção.
Verificação
awkdo workflow: 39 linhas,terminando certo no
## [2.4.0]npm test→ 38 passam · frontendnpm test→ 7 passamvite buildokO que este PR não resolve
Ele conserta o sintoma. O que impede a repetição vem em PR separado — porque
bumpar à mão pela terceira vez não é solução, é só adiar a quarta.