Updating version to 0.3.9 with timezone-js dependency version set to "<1"#11
Open
oGLOWo wants to merge 2 commits intomichaelahlers:masterfrom
Open
Updating version to 0.3.9 with timezone-js dependency version set to "<1"#11oGLOWo wants to merge 2 commits intomichaelahlers:masterfrom
oGLOWo wants to merge 2 commits intomichaelahlers:masterfrom
Conversation
…s a version number of ~0.4.7
|
Fixes issue #9 |
Author
|
@yguerro I changed the version for timezone-js to "<1" . I figured any 0.x.x up to 0.9.9 would likely not have breaking changes. I would say 1.x and up probably would. What do you think? |
oGLOWo
changed the title
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
2 participants
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.
Tag 0.3.9 exists on my fork. Could you please create it on your repo or pull mine in? The reason for this pull request is the hard version number on 0.3.8 for timezone-js set to 0.4.4. This wasn't playing nicely with automated builds since we would need to resolve dependency conflicts manually.