Skip to content
This repository was archived by the owner on May 13, 2020. It is now read-only.

Fix Windows release when using new release process #132

Merged
merged 1 commit into from
Nov 10, 2019
Merged

Conversation

SeanTAllen
Copy link
Member

Because skip_tags was set to true, we weren't starting a CI job
to do a release when a tag like 0.1.0 was pushed.

Removing skip_tags fixes the "no Windows release" problem encountered
during our most recent attempt at releasing.

Closes #128

Because `skip_tags` was set to true, we weren't starting a CI job
to do a release when a tag like `0.1.0` was pushed.

Removing `skip_tags` fixes the "no Windows release" problem encountered
during our most recent attempt at releasing.

Closes #128
@SeanTAllen SeanTAllen merged commit 3f762a1 into master Nov 10, 2019
@SeanTAllen SeanTAllen deleted the 128 branch November 10, 2019 15:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Appveyor setup doesn't trigger release
2 participants