Branch: refs/heads/master Home: https://github.com/phpmyadmin/scripts Commit: 5e03e958ecad1809b5bafb69dccca4724b0f268a https://github.com/phpmyadmin/scripts/commit/5e03e958ecad1809b5bafb69dccca47... Author: William Desportes <williamdes@wdes.fr> Date: 2026-11-10 (Tue, 11 November 2026) +01:00 Changed paths: M infrastructure/sentry/.env.dist M infrastructure/sentry/compose.yml Log Message: ----------- sentry: say the database password must be URL-safe The password is embedded verbatim in DATABASE_URL, and a "/", "#" or "?" in it makes the server fail at startup with "invalid port number", before it ever reaches PostgreSQL. `/` is the usual culprit: it is in the base64 alphabet, so an `openssl rand -base64` value breaks the deployment. Point at `openssl rand -hex 24` instead, in .env.dist and next to the DATABASE_URL it feeds. Verified against the image: "/", "#" and "?" fail parsing, while "+", "=", ":", "@", "&" and space pass through. Also give the postgres tmpfs to uid 70: the image's initdb chmods /var/run/postgresql and logged "Operation not permitted" without it. Signed-off-by: William Desportes <williamdes@wdes.fr> Co-Authored-By: DeepSeek <noreply@deepseek.com> Commit: bd00d559d3daba641a9fe74b1bdac3a366724a97 https://github.com/phpmyadmin/scripts/commit/bd00d559d3daba641a9fe74b1bdac3a... Author: William Desportes <williamdes@wdes.fr> Date: 2026-11-10 (Tue, 11 November 2026) +01:00 Changed paths: M phpmyadmin-report.php Log Message: ----------- reports: Paginate the GitHub and GitLab API calls Both calls made a single request. GitLab was worse: the commits query had no per_page at all, so Salsa returned its default of 20 and everything past the first page never reached the report. The output still looked complete, which is why it went unnoticed until a month had more than 20 commits in one project. GitHub already asked for per_page=100 but stopped there, so it would truncate the same way above 100. Both now follow pages until a short page comes back, and the GitLab commits query asks for 100 per page. Co-Authored-By: DeepSeek <noreply@deepseek.com> Commit: aaa3c7e7b98599acae91f52b27a3c4fe2b2fc1c1 https://github.com/phpmyadmin/scripts/commit/aaa3c7e7b98599acae91f52b27a3c4f... Author: William Desportes <williamdes@wdes.fr> Date: 2026-11-12 (Thu, 11 November 2026) +01:00 Changed paths: M phpmyadmin-report.php Log Message: ----------- Keep google-recaptcha only up to 2025-01 The project left the phpmyadmin-team namespace, so its history before that date is legitimate in a report but anything after is not phpMyAdmin's work any more. I had removed it in b83c52d27142df6adb1527fc98192881646f96d7 Co-Authored-By: DeepSeek <noreply@deepseek.com> Commit: aa31ce4ec2f417a6fb19189b6bbc99da53af4c83 https://github.com/phpmyadmin/scripts/commit/aa31ce4ec2f417a6fb19189b6bbc99d... Author: William Desportes <williamdes@wdes.fr> Date: 2026-11-12 (Thu, 11 November 2026) +01:00 Changed paths: M infrastructure/sentry/README.md M infrastructure/sentry/compose.yml Log Message: ----------- sentry: upgrade to 0.26.0 Bump the server tag and digest, and re-resolve every other digest: postgres and exim are unchanged upstream, which the comments now record. 0.26 needs one configuration decision and changes a few behaviours we relied on, all checked on a stack upgraded in place from 0.25 on the same cluster: - webhook and Slack alerts are confined to public addresses and proxy variables are ignored, so RUSTRAK_ALERTS_ALLOW_PRIVATE_NETWORKS is set to off explicitly. Email through the smtp relay is unaffected. - the legacy POST /api/<id>/store/ is accepted again, so the error-reporting server forwards without the envelope change. Only its sendFeedback(), which posts to /api/embed/error-page/, still gets a 404. - sessions moved to the database: everyone signs in once more. - GET /api/projects answers {"items": [...]} instead of a bare array. - /auth/register is gone and per_page above 100 answers 400. Verified: 30 checks pass against the bumped stack — migrations on the existing 0.25 data, both ingest endpoints, user_report feedback, alert email through the relay, /metrics 404, CapEff and CapBnd 0 with read-only rootfs, and no egress from db, mail or front while smtp keeps it. Signed-off-by: William Desportes <williamdes@wdes.fr> Co-Authored-By: DeepSeek <noreply@deepseek.com>