Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Release binaries get replaced after publishing, which breaks checksum pinning

Cerrado
  • ¿Algo no está bien?
#2,761 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker, github-actions, go
Área
ci-cd, release

Línea de trabajo

Start by reading the release workflows in .github/workflows (e.g. the Linux binary build job) to find what re-runs and re-uploads artifacts after a release is published, and check the release notes for v1.13.x to confirm rebuilds are intentional. Done looks like either a documented policy (release notes or docs) or a pipeline change: immutable uploads plus a SHA256SUMS file / build attestations per release. Coordinate with maintainers first since the fix touches release policy, not just code.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

We download frankenphp-linux-x86_64-gnu in our Dockerfile and pin it with ADD --checksum=.... Twice this week
our builds broke without us changing anything, because the file behind the same release tag had changed.

Looking at the GitHub API, it seems the Linux binaries get re-uploaded some time after each release goes out:

Release Published Current file uploaded
v1.13.0 Oct 4 Oct 16, 01:18 UTC
v1.13.1 Oct 16 Oct 21, 15:48 UTC
v1.13.2 Oct 21 Oct 23, 01:30 UTC
v1.13.3 Oct 23 Oct 24, 01:17 UTC

The checksums we had pinned vs. what's there now:

  • v1.13.2: 0d6cd414487d8f663b0d992d315b07b977b8467370fd8ec7b6f3ae7e4f64d91f → fcc805fc84f715a83a1abb56a7a62619ad30608907097df013d19c31506b213c
  • v1.13.3: a6ad4dccbcbebceabdb139fe54cd1f711968fc6b3331085bf634c642fa7fcd31 → 7d384c472e5e8975a2fa32376f5b25c3882a3297129857b2cf884d481598aa51

These are probably intentional rebuilds, but nothing tells us so, and from the outside a rebuilt file looks the same
as one that was tampered with. For now we've had to drop the checksum, which we'd rather not do.

A few things that would help:

  • If the re-uploads are on purpose, a note in the release notes would be great.
  • Even better: leave published files alone and put out a new patch release for a rebuild. GitHub's immutable releases
    setting would enforce that.
  • A SHA256SUMS file with each release (signed, or with build attestations) so people can check what they download.

Thanks for all the work on FrankenPHP!

Lenguaje dominante
Go
Estrellas
11.4k
Forks
499
Merge medio
2 d 5 h
PR fusionados (30 d)
43

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de php/frankenphp

Todos los issues de php/frankenphp

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.