Open
Conversation
the version range isn't valid, and ST3 is not really all that relevant these days anymore
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, I maintain the [default channel](https://github.com/wbond/package_control_channel for Sublime Text and am testing some new tooling to help manage the package listings. During that testing your package came up and it looks like the
package-control.jsonmight have an invalid sublime version range syntax. These days, with ST3 being not super relevant anymore, the simplest thing to do might be to remove that version? Alternatively,>=3092 <4000could be written as3092 - 3999and that would also be fine.