chore: release 2.3.0 - #29
Merged
Merged
Conversation
Minor: duas funcionalidades novas desde a v2.2.0 (recuperacao de senha e i18n das telas principais), alem de correcoes de seguranca e busca. A main acumulou 10 merges sem release - quem clonasse pela tag v2.2.0 pegava o projeto sem o rate limit de login, sem a correcao do idioma da busca e sem as correcoes do avatar. Ao entrar na main, o workflow de release cria a tag v2.3.0 e publica a GitHub Release automaticamente.
Contributor
There was a problem hiding this comment.
Pull request overview
Bumps the project version from 2.2.0 to 2.3.0 in both the backend and frontend packages so the release workflow can tag v2.3.0 and publish the GitHub Release.
Changes:
- Update
versioninbackend/package.jsonandfrontend/package.jsonto2.3.0 - Sync corresponding
versionfields in bothpackage-lock.jsonfiles
Reviewed changes
Copilot reviewed 2 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| frontend/package.json | Bumps frontend package version to 2.3.0. |
| frontend/package-lock.json | Syncs lockfile’s top-level and root package version to 2.3.0. |
| backend/package.json | Bumps backend package version to 2.3.0. |
| backend/package-lock.json | Syncs lockfile’s top-level and root package version to 2.3.0. |
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.
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.
Release 2.3.0
Bump minor (
2.2.0→2.3.0). Ao mesclar, o workflowrelease.ymlcria a tagv2.3.0e publica a GitHub Release com as notas geradas automaticamente.Por que agora: a
mainacumulou 10 merges sem release. Quem clonasse pela tagv2.2.0pegava o projeto sem o rate limit de login, sem a correção do idioma da busca e sem as correções do avatar.O que entrou desde a v2.2.0
Duas funcionalidades novas compatíveis → minor, conforme SemVer e a seção Versionamento do README.
Validação
Rodei na
mainantes do bump:Test plan
npm testenpm run buildna mainversion-syncdo CI valida)v2.3.0e a Release saíram automaticamente