Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Bump i18next-scanner from 4.2.0 to 4.3.0 #4318

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 16, 2023

Bumps i18next-scanner from 4.2.0 to 4.3.0.

Release notes

Sourced from i18next-scanner's releases.

v4.3.0

What's Changed

  • refactor: remove the traverse code in parseJSXElement to eliminate redundant calls for setting translation keys by @​cheton in i18next/i18next-scanner#250
  • chore: bump vinyl and vinyl-fs to the latest release to fix vulnerability issue by @​cheton in d54293b5d008cd2164d6f961a6a16280db6cfad2
  • refactor: call the defaultValue helper to determine the value of a translation key when parsing Trans components by @​cheton in bcfd2cd66396bbad6a213fefa685c3059d5f32fc

Full Changelog: i18next/i18next-scanner@v4.2.0...v4.3.0

Commits
  • 108d443 chore(release): publish
  • bcfd2cd refactor: call the defaultValue helper to determine the value of a translat...
  • d54293b chore: bump vinyl and vinyl-fs to the latest release to fix vulnerability issue
  • 9dbe663 refactor: remove the traverse code in parseJSXElement to eliminate redundan...
  • See full diff in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@otto-the-bot otto-the-bot enabled auto-merge (squash) July 16, 2023 00:39
Bumps [i18next-scanner](https://github.com/i18next/i18next-scanner) from 4.2.0 to 4.3.0.
- [Release notes](https://github.com/i18next/i18next-scanner/releases)
- [Commits](i18next/i18next-scanner@v4.2.0...v4.3.0)

---
updated-dependencies:
- dependency-name: i18next-scanner
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/i18next-scanner-4.3.0 branch from f2859a7 to 4e00243 Compare August 14, 2023 13:34
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 27, 2023

Superseded by #4380.

@dependabot dependabot bot closed this Aug 27, 2023
auto-merge was automatically disabled August 27, 2023 00:28

Pull request was closed

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/i18next-scanner-4.3.0 branch August 27, 2023 00:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant