Trigger CI - test if v0.14.0 package set still compiles due to newtype change #799
Conversation
This file contains 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.
A few changelog PRs are being held up because the
Newtypeclass was changed. This PR triggers CI to reveal all those issues.I also am making a minor change in this PR. The
shared.dhallfile existed to define one place to update themetadata.versionfield. However, I later moved that field topackages.dhallbecause contrib libraries needed to use a package set without changing anything else in that repo, and this was the only way to achieve that. However, I never removed theshared.dhallfile as a result. This PR removes that file and updated the other two dhall files, so that CI still works.