envoyproxy / envoyproxy/toolshed

Improve release publishing workflow

Aperta
#162 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Python
Stelle
12
Fork
24
Merge medio
6h 37m
PR unite (30g)
92

Descrizione

Currently we manually create releases and any package that is not marked `-dev` in its `VERSION` file gets published

This creates a lot of unwanted commits, and boilerplate tasks that are pretty annoying and potentially unnecessary.

One possible solution is to make it such that:

- When a PR lands on `main` if the `-dev` version has changed for one or more packages...
- CI creates a branch for a new release, updates the `VERSION` files and publishes the packages to the version indicated by the previous dev version/s

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.