flatpak-builder: v6 tag doesn't point to latest v6 release
davidmhewitt opened this issue · 4 comments
The typical convention for GitHub actions is for the v6 tag to point to the latest v6.x.x version. Currently, v6 points to the release from a couple of weeks ago with the issue overwriting the Flatpak branch.
This means that automated PRs to bump dependencies in workflow files, like dependabot are proposing bumping to the broken v6 tag, as they typically only bump major versions. See this PR against an elementary repo: https://github.com/elementary/appcenter-reviews/pull/448/files
See the GitHub Actions docs for further info on the conventions: https://github.com/elementary/appcenter-reviews/pull/448/files
I have no idea how to make v6 tag point to a v6.1.... maybe i should ditch all those v6x tags and switch to a v6 branch
You just push a new v6 tag pointing to the same commit that v6.1 points to.
Should be fixed now
Thank you!