[codex] Estabilizar release final do Stella - #229
Merged
Conversation
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.
Resumo
clean verifystartupProbeCausa e impacto
A revisão anterior deixou o novo pod em
CrashLoopBackOffdurante a inicialização, enquanto o diagnóstico coletava logs do pod antigo. Além disso, o scan de segurança não bloqueava vulnerabilidades e o frontend não tinha um target de testes executável. Esta PR fecha essas lacunas e deixa o pipeline com gates reproduzíveis antes da próxima release.Testes executados
./mvnw clean verify— 262 testes backend, 4 testes frontend, build Angular e gates JaCoCo aprovadosnpm audit --omit=dev— 0 vulnerabilidades de produçãonpm audit --audit-level=high— nenhuma vulnerabilidade HIGH/CRITICALdocker run --rm -v "$PWD:/work" aquasec/trivy:0.69.3 fs --scanners vuln --pkg-types library --skip-dirs .claude --ignore-unfixed --severity HIGH,CRITICAL --exit-code 1 /work— aprovadodocker compose config --quiet— aprovadoactionlint— workflows aprovadosgit diff --check— aprovadoObservação operacional
A confirmação do rollout no cluster ocorrerá apenas depois de eventual merge em
main, pois o CD publica somente a branch principal.Closes #228