Bump @tiptap/extension-highlight from 3.23.5 to 3.23.6 in /client#1084
Bump @tiptap/extension-highlight from 3.23.5 to 3.23.6 in /client#1084dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@tiptap/extension-highlight](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight) from 3.23.5 to 3.23.6. - [Release notes](https://github.com/ueberdosis/tiptap/releases) - [Changelog](https://github.com/ueberdosis/tiptap/blob/main/packages/extension-highlight/CHANGELOG.md) - [Commits](https://github.com/ueberdosis/tiptap/commits/v3.23.6/packages/extension-highlight) --- updated-dependencies: - dependency-name: "@tiptap/extension-highlight" dependency-version: 3.23.6 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Claudia-Anthropica
left a comment
There was a problem hiding this comment.
@dependabot Straightforward patch bump of @tiptap/extension-highlight to 3.23.6 — the change itself is fine. But run-tests / build is red because the client SBOM wasn't regenerated; see inline. One heads-up: 3.23.6 declares an exact peer dep on @tiptap/core@3.23.6 while core and the rest of the tiptap suite stay at 3.23.5, so the lockfile still resolves it against 3.23.5. Harmless for a patch and pnpm installs fine, but the suite is briefly out of lockstep. (The separate refresh failure is just the unconfigured SBOM bot, unrelated to this PR.)
| "@phosphor-icons/react": "2.1.10", | ||
| "@tiptap/core": "3.23.5", | ||
| "@tiptap/extension-highlight": "3.23.5", | ||
| "@tiptap/extension-highlight": "3.23.6", |
There was a problem hiding this comment.
@dependabot [high] run-tests / build fails here because the client SBOM is stale after this bump — the gate complains that client/sbom/ no longer matches now that package.json/pnpm-lock.yaml changed. Regenerate it with pnpm run sbom:force in client/ and commit the updated sbom/bom.json + sbom/.lock-hash. Dependabot won't do this itself, and the refresh_sbom workflow is currently broken, so it needs a manual commit.
🤖 Prompt for AI agents
In the client/ directory, the SBOM is stale after bumping @tiptap/extension-highlight to 3.23.6, which fails the run-tests / build check with "client/sbom/ is stale". Run pnpm run sbom:force and commit the regenerated client/sbom/bom.json and client/sbom/.lock-hash.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @tiptap/extension-highlight from 3.23.5 to 3.23.6.
Release notes
Sourced from @tiptap/extension-highlight's releases.
Changelog
Sourced from @tiptap/extension-highlight's changelog.
Commits
195b13fchore(release): publish a new stable version (#7854)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 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)