Please publish major version tags (similar to actions/checkout)

So basically, if you cut a v2 tag to match the sha in v2.2.0, and do that going forward, then we can keep our tag to v2 or we would have to migrate our tag to v2.2.0. Not a BIG deal, just something that can be avoided if this was part of the automated release process.

Some background.

We use renovatebot to search for new releases and we use the @v2 pin however renovate cannot look up the github-tags for @v2 in order to see if there is a new commit hash to bump up the version.

Technically we're at the same version since we manually bumped it.

I was wondering how it was even possible to use open-policy-agent/setup-opa@v2 without their being a v2 tag. I guess the v2 release must have been published from the v2.2.0 release without needing the tag ?

Here is the output in renovate.

{
  "warnings": [
    "Could not determine new digest for update (github-tags package open-policy-agent/setup-opa)"
  ]
}

{
  "autoReplaceStringTemplate": "{{depName}}@{{#if newDigest}}{{newDigest}}{{#if newValue}} # {{newValue}}{{/if}}{{/if}}{{#unless newDigest}}{{newValue}}{{/unless}}",
  "commitMessageTopic": "{{{depName}}} action",
  "currentDigest": "34a30e8a924d1b03ce2cf7abe97250bbb1f332b5",
  "currentValue": "v2",
  "datasource": "github-tags",
  "depName": "open-policy-agent/setup-opa",
  "depType": "action",
  "packageName": "open-policy-agent/setup-opa",
  "replaceString": "open-policy-agent/setup-opa@34a30e8a924d1b03ce2cf7abe97250bbb1f332b5 # v2",
  "versioning": "semver",
  "warnings": [
    {
      "message": "Could not determine new digest for update (github-tags package open-policy-agent/setup-opa)",
      "topic": "open-policy-agent/setup-opa"
    }
  ],
  "updates": []
},

Here is how actions/checkout does it https://github.com/actions/checkout/tags. They use a v4 tag to map to their latest v4.3.0 tag.

No files or tests are named in the issue. Start by inspecting the repository's release automation and existing tags, then determine where major-version tags are published; done means a v2 tag tracks the current v2.x release so Renovate can resolve its digest.