Document updating a pinned frameworkVersion in the v4 upgrade guide#417
Merged
Conversation
GrahamCampbell
force-pushed
the
document-frameworkversion-upgrade
branch
from
4640b4f to
7b5006f
Compare
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.
A serverless.yml that pins frameworkVersion to a v3 range causes every osls command to fail immediately with FRAMEWORK_VERSION_MISMATCH once osls v4 is installed, since the installed version no longer satisfies the pinned range. This is a common configuration because upstream Serverless Framework v3 templates shipped frameworkVersion set to 3, yet the upgrade guide never mentioned it. This adds a breaking-changes section explaining that the pin must be updated to a v4 range and noting that the check runs before configuration validation and so cannot be relaxed with configValidationMode.