chore(deps): bump eslint-plugin-jsdoc from 63.0.7 to 63.2.2 - #31
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump eslint-plugin-jsdoc from 63.0.7 to 63.2.2#31dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) from 63.0.7 to 63.2.2. - [Release notes](https://github.com/gajus/eslint-plugin-jsdoc/releases) - [Commits](gajus/eslint-plugin-jsdoc@v63.0.7...v63.2.2) --- updated-dependencies: - dependency-name: eslint-plugin-jsdoc dependency-version: 63.2.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Superseded by #37. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/eslint-plugin-jsdoc-63.2.2
branch
July 31, 2026 12:05
NSchatz
added a commit
that referenced
this pull request
Aug 4, 2026
`gate-refuter` pass 2 returned NOT REFUTED and still found that the trailing
comment strip added one commit earlier had turned a safe exit 2 into an
exit 0 ON AN INERT FILE:
"@cosyte/tsconfig": "none" # keep pinned
`js-yaml` strips the quotes, so `@changesets/parse` reads that as the
all-`none` shape the guard exists to refuse, while the guard compared the raw
token and cleared it. A green guard over a changeset that bumps nothing,
introduced by the commit that fixed green runs which did nothing.
The type is now unquoted before the comparison and validated against
`validVersionTypes`, so an unknown type (`patch#nospace`, which the comment
rule deliberately does not strip) takes exit 2 here instead of throwing inside
`changesets/action` halfway through a release. Three spellings of `none` are
pinned by a control.
Also from pass 2, all diagnostic or prose:
* The "bumped but never published" annotation asserted "the ones that did
publish have been tagged and released" unconditionally, including when an
earlier step failed and nothing published at all. It now names both readings
and only claims the successful ones when there are any.
* Deleted "a cancelled job" from the list of `gh release create` failure
causes: on a cancelled run `!cancelled()` is false and the step does not run.
* "changelog headings are derived from tags" described a manual practice as
automation. Now says "dated from tags by hand".
* Deleted a stale sentence claiming the post-publish step keys off the action's
own `published` output, which stopped being true when that step was rewritten.
The shared `cosyte/.github` release workflow was re-read a third time, at
`5896185` (PR #31, the post-publish install gate). Both reasons config cannot
call it are unchanged: its gate still answers "is a release pending" from the
ROOT package.json (this repo's is private, pinned at 0.0.0, and returns
`never-versioned`, which would withhold every publish), and it still hardcodes
`tag="v${version}"`. Its inputs offer no multi-package mode and no tag
override. That comment is now one sentence instead of an accreting list of
shas.
82 root + 75 package tests. actionlint clean.
NSchatz
added a commit
that referenced
this pull request
Aug 4, 2026
… overstatements `gate-refuter` pass 3 returned NOT REFUTED and found that the comment justifying why this repo cannot call the shared workflow measured an UNMERGED branch. It cited sha `5896185` and an `expect-unpublished-deps` input, both of which exist only on `cosyte/.github`'s `feat/post-publish-install-gate` (PR #31, still open), while the workflow next door names `release.yml@main` as the alternative. `main` is at `1e634f0` and has three inputs. The conclusion was never affected: both blockers were re-verified on `main` itself, so "config cannot call it" holds either way. But a citation reaching for a moving third-party branch is the third round running where a CLAIM about a measurement was the weak point rather than the code, so the fix is to delete the moving parts rather than update them. The comment now names `1e634f0` on `main` and says the reasons do not depend on an input at all. Also deleted, same reason: "halfway through a release run" and "mid-release". `@changesets/read` parses every changeset up front and lets the error propagate, so a bad release type kills the action BEFORE `changeset version` or `changeset publish`. Nothing would be half-released. The error string inside the guard was already accurate and is unchanged. Deliberately NOT changed, both raised by pass 3 as minor and neither a false green: two exit-code mis-assignments on inputs no tooling can produce (`"none"#x` takes 2 where the contract says 1; `"none'` with asymmetric quotes takes 1 where it says 2), and duplicate frontmatter keys passing the guard while js-yaml throws. The first is hardening after a passing verdict, which this repo family has been refuted for before; the second is pre-existing and loud. Both are backlog lines.
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 eslint-plugin-jsdoc from 63.0.7 to 63.2.2.
Release notes
Sourced from eslint-plugin-jsdoc's releases.
... (truncated)
Commits
3663803fix: update jsdoccomment and devDeps. (#1730)9fd2f28fix: update jsdoccomment, spdx-expression-parse, devDeps.; fixes #1727 (#1728)77a7b1afeat(normalize-see-links): add wrapBareUrls option (#1726)c03dd66feat: addnormalize-see-linksrule (#1725)786d12dfix(escape-inline-tags): ignore Markdown code spans3728347fix: failing pages build and deploymentdf5813cfix: CJS builds; fixes #17197676b50fix(require-jsdoc): skip overloads to find method comment blocks; fixes #1688008470dchore: update semver, devDeps.; test Node 2686ae048chore: use yargs 17.7.3 with release-age exclusionDependabot 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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)