chore(deps): bump i18next-fs-backend from 2.6.1 to 2.6.4#5352
Merged
asyncapi-bot merged 1 commit intomasterfrom Apr 22, 2026
Merged
chore(deps): bump i18next-fs-backend from 2.6.1 to 2.6.4#5352asyncapi-bot merged 1 commit intomasterfrom
asyncapi-bot merged 1 commit intomasterfrom
Conversation
Bumps [i18next-fs-backend](https://github.com/i18next/i18next-fs-backend) from 2.6.1 to 2.6.4. - [Changelog](https://github.com/i18next/i18next-fs-backend/blob/master/CHANGELOG.md) - [Commits](i18next/i18next-fs-backend@v2.6.1...v2.6.4) --- updated-dependencies: - dependency-name: i18next-fs-backend dependency-version: 2.6.4 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
✅ Deploy Preview for asyncapi-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
asyncapi-bot-eve
approved these changes
Apr 22, 2026
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5352 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 22 22
Lines 830 830
Branches 159 159
=========================================
Hits 830 830 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-5352--asyncapi-website.netlify.app/ |
codxbrexx
pushed a commit
to codxbrexx/website-asyncapi
that referenced
this pull request
May 5, 2026
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 i18next-fs-backend from 2.6.1 to 2.6.4.
Changelog
Sourced from i18next-fs-backend's changelog.
Commits
7f623072.6.4adf8a30security: hardening for 2.6.43bd0132update depsfd1616fBump fastify from 5.3.2 to 5.8.5 in /example/fastify (#67)8b6a5ba2.6.3957635duse own interpolation function27710832.6.22cd2c20use own interpolation functionDependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.