relase tagging

[systemcrash]

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:

Run boxpositron/upload-multiple-releases@1.0.7
Found 4 asset(s)
homer-app
homer-app-1.4.59-amd64.deb
homer-app-1.4.59-amd64.rpm
homer-ui-1.4.59.tgz
Resolving tag
Release exists, overwriting assets.
Overwriting homer-app
Uploaded homer-app
Overwriting homer-app-1.4.59-amd64.deb
Uploaded homer-app-1.4.59-amd64.deb
Overwriting homer-app-1.4.59-amd64.rpm
Uploaded homer-app-1.4.59-amd64.rpm
Overwriting homer-ui-1.4.59.tgz
Uploaded homer-ui-1.4.59.tgz

[lmangani]

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.

[systemcrash]

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

	steps:
	- uses: actions/checkout@v3
	- id: tag_bump
	name: Bump version and push tag
	uses: anothrNick/github-tag-action@1.39.0
	env:
	GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
	DEFAULT_BUMP: none
	BRANCH: master

DEFAULT_BUMP should be something like patch

https://github.com/anothrNick/github-tag-action

[systemcrash]

Check also the warnings for your GH actions which run, and bump some of those actions to newer versions.