-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
relase tagging #546
Comments
That's more or less the current status indeed. The CI/Release pipeline uses this floating release as a hooking point and not as a distribution medium for our setups which are all package repository based or container based. If this is important and useful we can of course create new releases instead, but in order to do so we should move this last remaining pipeline to github actiions. |
Just let the releaser auto-increment the version number when new features get added or PRs get merged, rather than keep adding features to the latest version release. master/latest is fine with everything new going in there. But nailing an image to a particular release version should be an option (so that e.g. checksums match). homer-app/.github/workflows/build.yml Lines 72 to 80 in 5327f33
|
Check also the warnings for your GH actions which run, and bump some of those actions to newer versions. |
I know release tagging isn't everyone's favourite thing to do, but the 1.4.59 release tagged in November has assets fresh from a few days ago... confusing:
Is this intended? That the latest versions inherits all the latest changes until... the next successive version?
Your GH action for PR #545 logs this:
The text was updated successfully, but these errors were encountered: