Support release candidate alias ("nextstable"?) as a moving target
Los mantenedores suelen responder en 5 días
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
- Bastante claro
- Estado de actividad
- Tranquilo
- Stack tecnológico
- github-actions, go, typescript
- Área
- ci-cd
Línea de trabajo
El issue no nombra archivos ni pruebas específicos. Empieza localizando la resolución existente de los alias stable y oldstable y sus pruebas, y luego sigue cómo se seleccionan las versiones de Go. Se considera terminado cuando nextstable selecciona el release candidate más reciente solo cuando es más nuevo que stable y, en caso contrario, no realiza pruebas innecesarias del release candidate.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description:
Currently setup-go supports "stable" and "oldstable" aliases. They are moving targets, so they make it convenient for repositories to target those versions, without needing to edit action.yaml whenever new major and minor Go releases come out.
I understand that it's already possible to target Go pre-release versions explicitly (see https://github.com/golang/go/issues/38773#issuecomment-4706881732; CC @qmuntal).
This feature request is for a similar moving target alias that makes it possible for a repository to configure action.yaml once and receive testing with the latest Go release candidate, whenever it is newer than the latest stable release.
Justification:
For context, note that Go only does release candidate pre-release types (it used to do betas, but by now those aren't done), which have a very high bar as noted at https://go.dev/s/release#june--december-week-2-release-candidate-1-issued:
A release candidate is meant to be as close as possible to the actual release bits. Issuing a release candidate is an indication that the Go team has high confidence that the tree is free of critical bugs. In particular, because Google continuously tracks the development version of Go, by the time a release candidate is issued, a close approximation of it will have been running in production at Google for at least a week or two.
[...]
We strongly encourage other organizations to test release candidates as aggressively as they are able and to report problems that they find.
Consider a repository that is set up as follows today:
go-version: 'stable'
If some upcoming major release of Go contains some regression that happens not to be caught by any other mechanism, but affects this particular repository with tests that catch the problem, then the current experience is that the repository owner may only find out about breakage once the final major Go release is released, and 'stable' begins to pick it up.
On the other hand, if it's convenient to pick a moving target alias like:
go-version: 'nextstable'
Then it would increase chances of this repository owner finding about a problem and reporting it, such that it can be fixed in time for a major Go release as opposed to in one of its subsequent minor releases (or a future major release, if the problem doesn't meet the bar for backporting).
Ideally, this 'nextstable' alias shouldn't do any work whenever there isn't a Go release candidate version newer than the latest stable Go release. (That is, there's no use in testing go1.26rc3 after go1.26.0 is out.)
Are you willing to submit a PR?
I'm not very familiar with the implementation and conventions within this repository, so I would prefer to let someone else who is interested to pick this up. Thanks.
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.8k
- Forks
- 684
- Merge medio
- 12 d 23 h
- PR fusionados (30 d)
- 3
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de actions/setup-go
-
Provide an option to skip the Go SDK tool-cache write for ephemeral / parallel self-hosted runnersAbiertofeature request
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
actions/setup-go#792 · 4 comentarios ·
Los mantenedores suelen responder en 5 días
-
Cache key incorrectly uses 'x64' instead of '386' when architecture is set to '386' on WindowsAbiertofeature request
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
actions/setup-go#749 · 2 comentarios ·
Los mantenedores suelen responder en 5 días
-
feature request
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
actions/setup-go#746 · 8 comentarios ·
Los mantenedores suelen responder en 5 días
-
go-version-file does not parse .mod files other than go.modPosiblemente ocupada @kaovilai la tomó hace 239 días. Abiertofeature request
Dificultad 2/5 1-3 horas Aptitud para principiantes 48/100
actions/setup-go#736 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 5 días
-
feature request
Dificultad 3/5 1-2 días Aptitud para principiantes 42/100
actions/setup-go#720 · 1 comentario ·
Los mantenedores suelen responder en 5 días
Todos los issues de actions/setup-go
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
solidjs/solid-docs#1716 ·
Los mantenedores suelen responder en 1 día
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Progress indicated by console logs is off by onePosiblemente ocupada @marceliwac la tomó hoy. Abiertobug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
aws-samples/aws-cdk-examples#1336 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
melgarafael/DeskcommCRM#4999 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
type: bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 2 días