fix: read schema version from package.json instead of non-existent --version flag#37
Merged
jorisjonkers-dev-agents[bot] merged 1 commit intoJul 9, 2026
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.
The deploy-artifact run.sh was calling
deploy-config-schema --versionto verify the installed package version, but the CLI does not support a--versionflag for displaying the tool version (it uses--versionas a bundle pack parameter). This causedinstalled=to be always empty, which in turn always triggered E_SCHEMA_VERSION_MISMATCH.Fix: read the version from the installed package.json directly using node, which is always present in the CI environment.