Files
inbraille/CHANGELOG.md
T
Lucas RayanandClaude Sonnet 5.5 a9aec5abe4
Release / Plano (reaproveitar a imagem?) (push) Successful in 8s
CI / Trivy (dependências, segredos e configuração) (push) Failing after 8s
Release / ci (push) Failing after 9s
CI / Testes e imagem Docker (linux/arm64) (push) Skipped
Release / Publica a imagem (linux/arm64) (push) Skipped
Release / Cria a release no Gitea (push) Skipped
Recover InBraille from the production image (1.3.1) and move it to Gitea
The GitHub account was suspended and the repository had no backup. The deployed code
(src/, public/, index.html, main.py, requirements.txt) was extracted from the production
image 1.3.1. The tests, Dockerfile, compose files, SECURITY.md, CHANGELOG.md and README were
rebuilt from the records of the work sessions that created them; LICENSE, .gitignore,
robots.txt and sitemap.xml were recreated. CI now runs on Gitea Actions.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-02 00:15:01 -03:00

3.3 KiB

Changelog

Everything notable in InBraille is recorded here. The format follows Keep a Changelog and the project follows Semantic Versioning.

Note on history. The original Git history and the project files that are not part of the container image were lost with the previous GitHub account. This repository was rebuilt on 2026-11-02 from the production image 1.3.1 (the exact deployed code in src/, public/, index.html and main.py) and from the records of the work sessions that created the tests, the Dockerfile, the CI and the documentation. Entries for 1.2.0 and 1.3.0 left no record and are described only by what the code shows.

Unreleased

1.3.2 - 2026-11-02

Changed

  • The code, the container image and the releases now live on Gitea (git.lucasrguerra.dev.br); the deployment pulls the image from its registry instead of GitHub Container Registry.
  • CI moved from GitHub Actions to the Gitea runners (.gitea/workflows): Trivy on the repository and on the image, the pytest suite in a Dockerfile test stage, an arm64 image build and a smoke test that exercises the pages, the SEO files, the API (including a real STL generation) and the production isolation (--read-only, no capabilities, non-root). The image is built once per content hash and reused by the release.
  • Dockerfile split into base, test and runtime stages; the runtime image is unchanged (Python 3.14, non-root user 10001, read-only friendly).
  • SECURITY.md: vulnerabilities are reported by e-mail instead of GitHub Security Advisories.
  • .gitattributes forces LF line endings.

Fixed

  • /robots.txt and /sitemap.xml returned 500 in production since the image never contained those files (the Dockerfile did not copy them). Both files are now part of the repository and the image, with the hreflang alternates for pt-BR, en and zh.

1.3.1

  • Fixed returning visitors running stale frontend code after a deploy: HTML and /public assets are now served with Cache-Control: no-cache so browsers revalidate them.
  • Release workflow now also pins INBRAILLE_VERSION for the Coolify preview environment, which was stuck on 1.1.0.

[1.3.0] and [1.2.0]

No changelog was kept for these releases, so nothing is claimed here beyond what survived: the sources of the live plate preview (public/preview.js) and of the browser-side STL generator (public/modules/client_stl_generator.js) are part of the deployed code.

1.1.0

  • STL generation now goes through a bounded FIFO queue instead of rejecting requests when busy.

1.0.0

  • First tagged release, published as a Docker image on GitHub Container Registry.
  • Security hardening of the API and the container (see SECURITY.md).
  • Dependencies upgraded; all Trivy findings (critical, high and medium) resolved.