Feature/release automation #1778
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/tuist/stats/gth0okp5a |
fortmarek
force-pushed
the
feature/release_automation
branch
from
eea89bc
to
3a124d5
Compare
|
@all-contributors add @fortmarek for ideas |
|
@pepibumur I've put up a pull request to add @fortmarek! 🎉 |
|
|
||
| - Major if there's been a breaking change. | ||
| - Minor by default. | ||
| - Patch if it's a hotfix release. | ||
|
|
| on: | ||
| push: | ||
| tags: | ||
| - '*' |
There was a problem hiding this comment.
@fortmarek should this be triggered every Friday at 10:00 and let Tapestry do the tagging?
There was a problem hiding this comment.
tapestry github-release version is the command that should be triggered continuously - but I'd first do one or two releases manually to validate that the process is working as intended and then we can take the automation one step further
|
@all-contributors add @fortmarek for ideas |
|
@pepibumur I've put up a pull request to add @fortmarek! 🎉 |
Short description 📝
Creating a release should be an automated process. Ideally, we should not even think about creating a new release and it should be done eg. every Friday.
Solution 📦
For this task we can use tapestry which now has a github action, too. As the first step, I'd run
tapestrymanually and once we validate it all works we can run the release automatically without us even doing anything.