envoyproxy / envoyproxy/toolshed

Improve release publishing workflow

Open
#162 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
12
Forks
24
Avg merge
6h 37m
Merged PRs (30d)
92

Description

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.