Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto release every change (continuous delivery) #242

Open
docwhat opened this issue Apr 6, 2023 · 2 comments
Open

Auto release every change (continuous delivery) #242

docwhat opened this issue Apr 6, 2023 · 2 comments

Comments

@docwhat
Copy link
Contributor

docwhat commented Apr 6, 2023

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:

  1. Ensure the branch protections are up-to-date.
  2. Ensure the test coverage is sufficient for confidence.
  3. Write a CI workflow to tag and release a version based on comments. Something like Release Please could be used with conventional commits.
  4. Write documentation.
  5. Profit!
@docwhat docwhat changed the title Auto release every change Auto release every change (continuous delivery) Apr 6, 2023
@sxlijin
Copy link
Contributor

sxlijin commented 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.

@docwhat
Copy link
Contributor Author

docwhat commented Apr 7, 2023

That would be important to fix. 😳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants