Repository navigation
Release automation #232
Description
I noticed fixes are being merged, but they are not getting released, so I'd like to propose automating the releases here. The model that I'm proposing is one that we are following with Tuist for open source repositories that are not that actively maintained, and it's worked quite well. Here's the idea:
- We have a set of labels that we can use in PRs to indicate the type of change (e.g.
changelog:fixed). - On merge, we use git-cliff to determine if there are releasable changes (which we can identify through the labels)
- If so, we tag the commit, create the release notes, and create a new release on GitHub.
The role of maintainers would be to ensure the right label is being applied based on the type of change.
Activity
pepicrft commentedon Jun 11, 2025
Thoughts @AvdLee / @aleksandergrzyb ?
pepicrft commentedon Jun 11, 2025
With the above issues like this one would go away.
pepicrft commentedon Jun 11, 2025
BTW, @aleksandergrzyb could you also make @fortmarek a collaborator of the repo? We are both using and XCLogParser actively and had to create a fork to iterate on some improvements. We want to bring those back instead of working from a fork.
aleksandergrzyb commentedon Jun 11, 2025
@fortmarek was added and I agree that automatic release process would be a great addition!
AvdLee commentedon Jun 16, 2025
@pepicrft your proposal makes total sense to me! 🚀