Skip to content

Conversation

@mrnugget
Copy link
Contributor

I've realized that the cause for the sporadic "artifact already exists"
error messages when releasing is that Travis runs releases on both the
latest and the version-specific tag.

This only runs releases when on the version-specific commit.

I've realized that the cause for the sporadic "artifact already exists"
error messages when releasing is that Travis runs releases on both the
`latest` and the version-specific tag.

This only runs releases when on the version-specific commit.
@mrnugget mrnugget merged commit e1bc92a into master Apr 23, 2020
scjohns pushed a commit that referenced this pull request Apr 24, 2023
I've realized that the cause for the sporadic "artifact already exists"
error messages when releasing is that Travis runs releases on both the
`latest` and the version-specific tag.

This only runs releases when on the version-specific commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants