CompatHelper: add new compat entry for "TOML" at version "1.0" #653
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
guimarqu
approved these changes
Apr 1, 2022
…18-789-4156876630
Codecov Report
@@ Coverage Diff @@
## master #653 +/- ##
=======================================
Coverage 85.63% 85.63%
=======================================
Files 48 48
Lines 5403 5403
=======================================
Hits 4627 4627
Misses 776 776 Continue to review full report at Codecov.
|
guimarqu
deleted the
compathelper/new_version/2022-04-01-00-53-18-789-4156876630
branch
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.
This pull request sets the compat entry for the
TOMLpackage to1.0.This is a brand new compat entry. Previously, you did not have a compat entry for the
TOMLpackage.Note: I have not tested your package with this new compat entry. It is your responsibility to make sure that your package tests pass before you merge this pull request. Note: Consider tagging a patch release immediately after merging this PR, as downstream packages may depend on this for tests to pass.