Build mechanism

[DavidGOrtega]

Github actions needs by convention to override the mayor version doing a forced push.
Now it's done manually and should be done in the CI when merging into master.

[0x2b3bfa0]

Perhaps related to #31 and the infamous iterative/setup-dvc#12, because of the automatic major tagging system:

uses: Actions-R-Us/actions-tagger@v2
env:
  GITHUB_TOKEN: ${{ github.token }}
with:
  publish_latest_tag: true

[0x2b3bfa0]

Quote from @casperdcl #42 (comment)

The tagging approach for actions is very different from tags on normal repos.

• https://github.com/Actions-R-Us/actions-tagger is rubbish
• git push origin :refs/tags/{tag} && git tag --force {tag} && git push origin {main} --tags is also rubbish

You need git tag v1.x.x && git tag -f v1 && git push --tags -f

I would suggest:

• closing this PR unmerged
• rename master to v1 and use a hybrid of
  • branch approach for actions for major (i.e. @v1, @v2) pointers
  • tags for semver (i.e. @v1.x.x) pointers
    • ideally start writing release notes for these but accept that no workflow.yml file can enforce this

[0x2b3bfa0]

🔔 @iterative/cml, does anybody dislike this approach? In the meanwhile, I'm going to request again ⚡ permissions on the almighty #infrastrutcure channel.