Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

"invalid config Tag must not be a SemVer range" should be an error, not a WARN #7075

Closed
othiym23 opened this issue Jan 7, 2015 · 2 comments
Closed

"invalid config Tag must not be a SemVer range" should be an error, not a WARN #7075

othiym23 opened this issue Jan 7, 2015 · 2 comments
Labels
feature-request patch-welcome

Comments

@othiym23
Copy link
Contributor

othiym23 commented Jan 7, 2015

In other words, it should cause an early failure rather than publishing without the tag. See #6837 (comment) for context.

/cc @smikes
@othiym23 othiym23 mentioned this issue Jan 7, 2015
Closed
This was referenced Jan 7, 2015
Closed
Closed
This was referenced Mar 13, 2015
Closed
Closed
@kenany
Copy link
Contributor

kenany commented Mar 13, 2015

Fixed by #7099?

@othiym23
Copy link
Contributor Author

Indeed, fixed by 4ef1412. Thanks, @kenany!

@rvagg rvagg mentioned this issue Mar 19, 2015
Closed
@julianduque julianduque mentioned this issue Mar 20, 2015
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-request patch-welcome
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@othiym23 @kenany