Bump melbinjp/docproof from 0.1.1 to 0.2.2 in the github-actions group - #44
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Bump melbinjp/docproof from 0.1.1 to 0.2.2 in the github-actions group#44dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the github-actions group with 1 update: [melbinjp/docproof](https://github.com/melbinjp/docproof). Updates `melbinjp/docproof` from 0.1.1 to 0.2.2 - [Release notes](https://github.com/melbinjp/docproof/releases) - [Commits](melbinjp/docproof@v0.1.1...v0.2.2) --- updated-dependencies: - dependency-name: melbinjp/docproof dependency-version: 0.2.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
github-actions Bot
pushed a commit
that referenced
this pull request
Sep 1, 2026
…o do (#47) Dependabot opened #44 to move this from v0.1.1 to v0.2.2. Two things are wrong with taking it. It is already stale, because docproof is on v0.2.4. And moving between tags is the practice docproof's README argues against, in its own words: a tag is movable, so whoever controls that repository can change what @v0.2.4 means without a diff for anyone to review. Azul's maintainer raised exactly that against docproof itself, and it was fixed there. This repository was still on a tag while the tool it runs tells everyone else not to be. That is the shape of defect docproof exists to find, in the repository that runs it. Pinned to 5798f6a, which is what v0.2.4 resolves to today, with the tag in a trailing comment so a reader can see which release it is. Measured before bumping, not assumed: docproof v0.2.4 on this tree reports 126 claims checked and nothing contradicted, judging 15 of 17 documentation files.
Author
|
Looks like melbinjp/docproof is no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/github_actions/github-actions-e515550cad
branch
September 1, 2026 10:23
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
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.
Bumps the github-actions group with 1 update: melbinjp/docproof.
Updates
melbinjp/docprooffrom 0.1.1 to 0.2.2Release notes
Sourced from melbinjp/docproof's releases.
... (truncated)
Commits
22c1a4a0.2.2, because its own header was not valid UTF-8 when redirectedd3c10bc0.2.1, which exists so that pip install docproof resolvesfd63ce2Point the README at the writing about this tool42e937dA translated docs tree is an overlay, so the untranslated page still ships13d5195Name the other destination when a rename was a split3c1bbdfJudge link targets, which are the wrong paths a reader actually clicks2ea9eefReading eleven false positives beat two invented mechanisms6535f49The pre-registered test passed, and it cut my own headline by fourteen pointsdc2f03eThe gate that is worth 26 points of precision, and it is a genre not a verifier8b135f6A directory that was emptied for good is not a directory that might refill (#29)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions