You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub releases can reference an annotated tag, which is a git object that points to another git object. Currently, we assume that the annotated tag points to a commit:
return"", fmt.Errorf("could not resolve tag %q to commit: returned type is not 'commit'", tagName)
}
However, an annotated tag can point to another annotated tag (which then points to a commit), which is a case we don't handle. In general, there could be an arbitrarily long chain of tags before resolving to a commit.
GitHub releases can reference an annotated tag, which is a git object that points to another git object. Currently, we assume that the annotated tag points to a commit:
github-release-resource/github.go
Lines 298 to 309 in af189e0
However, an annotated tag can point to another annotated tag (which then points to a commit), which is a case we don't handle. In general, there could be an arbitrarily long chain of tags before resolving to a commit.
example problematic release - https://github.com/opencontainers/runc/releases/tag/v1.0.0-rc90
The text was updated successfully, but these errors were encountered: