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

Security Releases

Abierto
#1,017 4 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, shell
Área
devops, release, security

Línea de trabajo

The issue is about the release pipeline for Docker images. Look at the repository's GitHub Actions workflows, Dockerfile, and release scripts to understand the build and publish process. Investigate how security releases are coordinated with the WordPress security team and what automation can be added to reduce the delay. The goal is to propose a process improvement or automation change.

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

Descripción

Hello,

Given yesterdays 7.1.2 security release I was wondering why there was a delay it getting a Docker image with the fix in place released.

The news release with the 7.1.2 release was published at around 14:00 UTC and we didn't see a Docker image pushed with that release until around 20:00 UTC a 6 hour gap.

This was a severe security vulnerability that explicitly called out Docker image in the release notes: "The official php image for Docker is affected". (https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-7hp8-65ch-5whp).

How can we in future reduce this delay? I would have thought the WordPress security team would have given a heads up to the team that builds the docker images so that a 7.1.2 docker image was available immediately.

Thanks,
Stephen

Lenguaje dominante
Shell
Estrellas
2k
Forks
1.1k
Sin PR fusionados en 30 d

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

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 docker-library/wordpress

Todos los issues de docker-library/wordpress

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.