opral
move fink, manage, and badge to changeset based deployment
Problem
Fink deploys on every commit to main, which leads to:
- deployment of unreleased changes yet e.g. the SDK
- the infamous "don't push on Friday" problem
Proposal
- Don't auto-deploy on changes.
- Force changesets
- Have a CI action that deploys fink when the version increases
- [ ] fink
- [ ] manage
- [ ] badge
cc @janfjohannes (because we discussed this)
@NiklasBuchfink 1. agree?
- I assigned you because @flornkm is gone. If you implement it for Fink, you should be able to re-use the logic for manage and badge too
Let's do this 👍🏼 I see the benefits and we need better quality this year.
@samuelstroschein thanks its a really good idea, render will internally build a docker image for each service that is bumped in version and keep that in the deployment history, so if this works out, this is effectively like a small version of the docker setup i had in mind. i think the next step is to add the changeset workflow into our own ci as the github action runner we use at the moment is very slow, unreliable and noisy on prs. it should not be too hard to do.
@janfjohannes i think the next step is to add the changeset workflow into our own ci as the github action runner we use at the moment is very slow, unreliable and noisy on prs. it should not be too hard to do.
Let's evaluate https://rushjs.io/ before we build too much infra for changesets.
- changesets is unmaintained
- rush seems to solve many problems all at once
- rush has baking from Microsoft, TikTok, Big tech (will not go unmaintained)
@janfjohannes should we spare time investigating rush?
@samuelstroschein sure lets give a try if we can replace nx with rush and get changeset features on top
@NiklasBuchfink assigned you as you are already working on version / hash display in fink
duplicate in linear https://linear.app/opral/issue/FINK-5/move-fink-manage-and-badge-to-changeset-based-deployment