chore: adopt the published 0.8.0 in the bundlers and the example app - #602
Merged
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
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.
Follow-up to #600. The two bundlers and the example app take the published 0.8.0.
A caret range does not cross a minor before 1.0, so
^0.7.0excludes0.8.0. The example app already calls the 0.8.0buildEpCtx(session)signature, so until this lands it is out of step with the version it installs.The lockfiles are a separate commit because they pin the published tarball. Each records the shasum npm reported for 0.8.0. The package's dependencies are unchanged from 0.7.0, so only that entry moves.
Merging this changes what the loader bundles for every app host on the next server deploy. #599 keeps the managed form working for hosts whose own server is still on an earlier version.