Build the site against idfkit 1.0.0-rc.3 - #8
Merged
Conversation
Contributor
Author
|
Docs preview for this PR is available at: |
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.
idfkit 1.0.0-rc.3 was released, so
[tool.idfkit.library]and the pinned dependency advance from0.15.0.
Opened automatically by
notify-downstream.ymlin idfkit. Nobodyasked for it, which is the point: a release that renames a documented
interface makes pages wrong the moment it ships.
The checks on this pull request decide whether the pages survive
the new version. If they are red, a page describes something this
release no longer has under that name. Fix the page. Do not relax the
check, do not pin the level back, and do not merge past it.