Resource versions created with both SHA1 and tag, preventing tag_filter and tag_regex from working

What happened?

• With this resource:

  - name: mirrors_github_pinniped
    type: git
    icon: github
    tags: [ pinniped-ci-calatrava ]
    source:
      uri: git@gitlab.whatever.com:akeesler/fake-mirrors_github_pinniped.git
      tag_regex: v[0-9]+\.[0-9]+\.[0-9]+ # e.g., v0.4.1
      private_key: REDACTED

• I see these resource versions:
  

• Because of this, the next vx.y.z tags that I pushed to the repo did not show up as a resource version because the latest resource version has a ref of a SHA1 which filtered out all tags at this line: https://github.com/concourse/git-resource/blob/30c1e237dd9f919c71230501c771b4188383b51d/assets/check#L161.

What did I expect to happen?

• I hoped to see only resource versions with a ref matching my tag_regex.

Notes

• Not sure if this functionality has more to do with this git resource type, or the concourse resource checker.
• I am working with Concourse 7.0.0 at https://hush-house.pivotal.io.

Start at assets/check around line 161 and reproduce the configuration with tag_regex and a repository containing matching tags. Trace how the latest resource version ref is selected and verify that completed behavior exposes only versions whose refs match the requested tag filter or regex, including tags added afterward.