docs: documentar validacao com testcontainers e politica de retencao no readme - #13
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8f9822fbac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
|
|
||
| Official multi-architecture Docker images (`linux/amd64` and `linux/arm64`) are published automatically to the GitHub Container Registry (GHCR): | ||
| Official multi-architecture Docker images (`linux/amd64` and `linux/arm64`) are published automatically to the GitHub Container Registry (GHCR) on pushes to `master` with changes in `src/`. An automated retention policy maintains strictly the last 3 versions: |
There was a problem hiding this comment.
The policy does not maintain strictly three image versions: .github/workflows/release.yml configures keep-n-tagged: 3 while excluding latest, and the workflow comments explicitly state that latest is outside the count. After several releases, the current latest image plus three additional tagged versions can therefore survive, so this new guarantee understates actual registry retention.
Useful? React with 👍 / 👎.
| # Run Testcontainers validation suite | ||
| python3 -m unittest tests/test_container.py -v |
There was a problem hiding this comment.
When 9rtksync:test already exists locally, this command does not validate the generated image for the current checkout: obter_ou_construir_imagem() in tests/test_container.py returns immediately for any matching cached image and never rebuilds it. A developer rerunning the documented suite after changing src/ or the Dockerfile can therefore get a passing result against stale code; the instructions should explicitly rebuild/remove the tag, or the test should always build the current checkout.
Useful? React with 👍 / 👎.
1 participant
Atualiza o README.md com a documentacao de execucao dos testes com Testcontainers (Option 3) e as informacoes sobre a publicacao automatica no GitHub Packages e politica de retencao das 3 ultimas versoes.