chore(deps): bump @easyops-cn/docusaurus-search-local from 0.55.2 to 0.55.3 in /website in the website group - #5718
Merged
norman-abramovitz merged 1 commit intoJul 29, 2026
Conversation
Bumps the website group in /website with 1 update: [@easyops-cn/docusaurus-search-local](https://github.com/easyops-cn/docusaurus-search-local/tree/HEAD/packages/docusaurus-search-local). Updates `@easyops-cn/docusaurus-search-local` from 0.55.2 to 0.55.3 - [Release notes](https://github.com/easyops-cn/docusaurus-search-local/releases) - [Commits](https://github.com/easyops-cn/docusaurus-search-local/commits/v0.55.3/packages/docusaurus-search-local) --- updated-dependencies: - dependency-name: "@easyops-cn/docusaurus-search-local" dependency-version: 0.55.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: website ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
norman-abramovitz
pushed a commit
that referenced
this pull request
Jul 29, 2026
`check` asked whether any fragment mentions dependencies, which goes quiet the moment one does — including for bumps that merge afterwards. #5718 hit exactly that: fragment 0030 accurately covered #5716's website group, and its mere existence silenced the report for the later docusaurus-search-local bump, which reached develop with no note and no warning. Coverage is now the newest dep-mentioning fragment's commit time against the newest bump's. A fragment can only describe what landed before it, so a bump arriving later is uncovered until someone touches the fragment again. This also subsumes the stale-fragment limit the old comment documented: a leftover from a published window is older than every bump in the current one. The fragment side stays a loose text match, so prose rewritten away from the raw subjects still counts. A fragment git has no record of is being written right now and covers everything, which also keeps the check quiet when FRAG_DIR sits outside the repo. Tests move their fragments inside the throwaway repo and commit them at pinned dates — outside it, every coverage assertion passed through the uncommitted fallback and proved nothing. 17 -> 23.
norman-abramovitz
pushed a commit
that referenced
this pull request
Aug 6, 2026
Nine of the eleven bumps in the window had no fragment describing them. The other two (#5716, #5718) are already covered by 0030-website-deps-bump.md and are left out rather than double-reported. The x/text, x/net and oras-go CVEs are in the shipped backend tree and go under [Security Updates]; the frontend and website sweeps are build-chain only, per their commit bodies, and stay in [Chores].
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.
Bumps the website group in /website with 1 update: @easyops-cn/docusaurus-search-local.
Updates
@easyops-cn/docusaurus-search-localfrom 0.55.2 to 0.55.3Release notes
Sourced from @easyops-cn/docusaurus-search-local's releases.
Commits
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