Add PowerIO as a hard dependency#57
Merged
Merged
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.
Summary
PowerIOto the package[deps]list.PowerIO = "0.0.1"to[compat], matching the pending General registry entry in New package: PowerIO v0.0.1 JuliaRegistries/General#157692.Why
PowerDiff should install PowerIO as a hard dependency once the PowerIO registration is approved. Until JuliaRegistries/General#157692 merges, CI is expected to remain blocked on resolving
PowerIO; after the registration lands, the compat bound should become satisfiable and the PR can merge normally.Validation
git diff --checkProject.tomland asserted the PowerIO UUID/compat values.Pkg.test("PowerDiff")against a temporary registry overlay mirroring New package: PowerIO v0.0.1 JuliaRegistries/General#157692; tests passed withPowerIO v0.0.1.