fix(releases): more reliable releases #1653
Conversation
luhring
commented
Nov 15, 2024
luhring
commented
- Consolidate release workflows into one
- Continue to use a scheduled check for new changes
- Also allow manual triggering of release creation
luhring
force-pushed
the
unfck-releases
branch
2 times, most recently
from
263dc57 to
66c35c5
Compare
- Consolidate release workflows into one - Continue to use a scheduled check for new changes - Also allow manual triggering of release creation Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
luhring
force-pushed
the
unfck-releases
branch
from
66c35c5 to
d89edf5
Compare
Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
|
do we really need daily releases? what changes are we needing to release daily and would it make sense to refactor the repo into a library and cli such that downstream can depend on something a bit more stable? |
The short answer is that we do tend to make updates to melange fairly often (daily is not unusual) that we want to bring into other tools and services. I'm not married to daily — but note that this isn't new as of this PR, this PR is just trying to get releases working like we meant for them to before. |
agree this isnt new, but its a pain in mono trying to stay up to date with this dep, especially when there are breaking api changes. i just want to raise attention to the churn daily releases creates downstream |
|
once a week may be fine to release an on-demand |
Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
