Problem: why does the example not work??
Users see the package on the Typst universe, click on the homepage, land on the repo and get shown an unreleased version, causing confusion when trying to use the example provided in the readme.
Solution: moar branches!!
Exactly on the next release (probably 0.4.0):
- Rename
main→next - Create a new branch
release - Make
releasethe default branch in the Codeberg UI - Bump the version in
next - mreow
A new release is then just fast-forwarding release to next.
Potential issue
Contributors might get confused and accidentally try to PR to the release branch. Maybe there is some setting in the Codeberg UI to configure the release branch as untargetable? Albeit that doesn't stop somebody from locally branching off and then getting confused on push. Hmm.
Probably doesn't matter all that much anyway, given that exactly 0 entities contributed via PRs so far.
### Problem: why does the example not work??
Users see the package on the Typst universe, click on the homepage, land on the repo and get shown an unreleased version, causing confusion when trying to use the example provided in the readme.
### Solution: moar branches!!
Exactly on the next release (probably 0.4.0):
1. Rename `main` → `next`
2. Create a new branch `release`
3. Make `release` the default branch in the Codeberg UI
4. Bump the version in `next`
5. mreow
A new release is then just fast-forwarding `release` to `next`.
#### Potential issue
Contributors might get confused and accidentally try to PR to the `release` branch. Maybe there is some setting in the Codeberg UI to configure the `release` branch as untargetable? Albeit that doesn't stop somebody from locally branching off and then getting confused on push. Hmm.
Probably doesn't matter all that much anyway, given that exactly 0 entities contributed via PRs so far.