Fix handling of pre-releases in frameworkVersion validation #8166
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.
Some of our tests (https://github.com/serverless/serverless/pull/8163/checks?check_run_id=1057358350) in v2 pre-release branch got broken when
frameworkVersion
was unconditionally added to serverless configurations.It's due to pre-releases not being matched by
*
version range (reason unknown -> npm/node-semver#329)This patch ensures, that
*
matches pre-releases as well.Additionally provided workaround for EFS integration test CI fail: https://github.com/serverless/serverless/runs/1056731807