feat: meteor 3.0.4 #27
Merged
Conversation
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
Julusian
force-pushed
the
feat/meteor-3
branch
from
2a40306 to
97d4dbb
Compare
Julusian
force-pushed
the
feat/meteor-2.16
branch
from
b87c082 to
6aa4104
Compare
Julusian
force-pushed
the
feat/meteor-3
branch
from
97d4dbb to
23ae564
Compare
Julusian
force-pushed
the
feat/meteor-3
branch
2 times, most recently
from
8dfb464 to
90ac781
Compare
Julusian
force-pushed
the
feat/meteor-3
branch
from
90ac781 to
692339c
Compare
Julusian
force-pushed
the
feat/meteor-3
branch
from
5839911 to
20ef99d
Compare
Julusian
force-pushed
the
feat/meteor-3
branch
from
20ef99d to
07489d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Builds on #26
This breaks support for the old showstyle/studio blueprint migrations (but not system). This is simply to avoid working through them and updating them to be async. I am hoping that their presence can be discussed with NRK, perhaps it is acceptable to remove them instead (this was the goal with the validateConfig and applyConfig methods)