You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose that this repository moves to a continuous delivery model where every change/commit accepted into main and passes all the CI tests will trigger a release automatically.
This should be possible now that there is test coverage and good linting (trunk!).
The use case for this is PR #237, which breaks hadolint on arm64 macOS systems. Not that big a deal if updating, but on a new project is a pain and is confusing. A CD setup would have this fixed within minutes of #237 being approved and merged.
A quick estimate of the work required:
Ensure the branch protections are up-to-date.
Ensure the test coverage is sufficient for confidence.
Write a CI workflow to tag and release a version based on comments. Something like Release Please could be used with conventional commits.
Write documentation.
Profit!
The text was updated successfully, but these errors were encountered:
docwhat
changed the title
Auto release every change
Auto release every change (continuous delivery)
Apr 6, 2023
Hey there - we definitely agree that this is something we want to work towards.
Unfortunately, there's still some delicate synchronization of the plugins & CLI releases that we have to do ourselves (we've released backwards-incompatible changes almost every month) so the releases aren't truly decoupled right now, and we'd have to address that in addition to this.
I propose that this repository moves to a continuous delivery model where every change/commit accepted into
main
and passes all the CI tests will trigger a release automatically.This should be possible now that there is test coverage and good linting (trunk!).
The use case for this is PR #237, which breaks
hadolint
on arm64 macOS systems. Not that big a deal if updating, but on a new project is a pain and is confusing. A CD setup would have this fixed within minutes of #237 being approved and merged.A quick estimate of the work required:
The text was updated successfully, but these errors were encountered: