Repository navigation
#6: Drop deprecated techpack.yaml component keys - #7
Merged
Merged
Conversation
- mcs ignores both and installs components in declaration order - Clears the six registry validation warnings (#6)
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
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.
Why
The MCS registry flags six warnings because the manifest still declares
isRequiredanddependencies. mcs ignores both and installs components in declaration order, so the warnings sort the pack below clean ones without changing any behaviour. Components are already declared in dependency order, so install order doesn't change.Fixes #6
Test plan
mcs syncin a project using the pack → expect the hooks and runtime library to install as before