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.
This integrates two dependencies of ImagineInterface: ImagineHardware and UnitAliases.
The reason I'm not including ImagineInterface in this PR is that I don't want to lock us into a particular ImagineInterface sha until I see that tests pass for my latest PR. And I can't check whether tests pass without adding these dependencies to the registry. In this case it's no big deal, but this kind of workflow could lead to tedium in the future: I think this means that if we update multiple packages in the dependency tree at the same time then we'll need to make several incremental PRs here in the registry if we want to be sure that CI tests pass before merging changes (and generally we do want that).