feat: deploy front to Vercel production - #61
Merged
Conversation
caioplaninschek
marked this pull request as ready for review
June 25, 2026 17:23
caioplaninschek
requested review from
IgorRocha1603,
LucasAlmeida151704,
eduoncode,
fernandaclass,
gabriel-varela,
joaovictorBC and
luizpassaroni
June 25, 2026 17:28
gabriel-varela
approved these changes
Jun 25, 2026
fernandaclass
approved these changes
Jun 25, 2026
fernandaclass
approved these changes
Jun 25, 2026
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
3 participants
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.
Closes #38
O que muda
Registra a URL de producao no README. O deploy foi feito via Vercel CLI — nenhuma mudanca de codigo foi necessaria (o front ja apontava para o back via env server-side).
Deploy
API_INTERNAL_URL,INTERNAL_API_KEY— semNEXT_PUBLIC_, segredo nunca chega ao browser.Validacao e2e (producao)
Fluxo P0 executado no ambiente publicado:
Check de nao-vazamento: zero requisicoes diretas ao backend a partir do browser; sem segredo/URL interna nos 110 chunks JS do client.
Como testar
Acesse https://lab-dev-software-front.vercel.app e percorra o fluxo acima.