Update eslint-plugin-react-refresh 0.4.20 → 0.4.22 (minor)#43
Merged
guibranco merged 2 commits intoOct 1, 2025
Merged
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
|
You've used up your 5 PR reviews for this month under the Korbit Starter Plan. You'll get 5 more reviews on October 5th, 2025 or you can upgrade to Pro for unlimited PR reviews and enhanced features in your Korbit Console. |
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
github-actions
Bot
added
the
size/S
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Here's the code health analysis summary for commits Analysis Summary
|
gstraccini
Bot
added
the
☑️ auto-merge
![gstraccini[bot]](https://avatars.githubusercontent.com/in/480132?s=60&v=4){kind=small}
guibranco
approved these changes
Sep 26, 2025
Owner
guibranco
left a comment
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
Owner
|
@depfu merge |
depfu
Bot
force-pushed
the
depfu/update/npm/eslint-plugin-react-refresh-0.4.22
branch
from
fc09cc5 to
7762f78
Compare
|
Infisical secrets check: 🚨 Secrets leaked! Caution The Infisical CLI tool found secrets leaked in your repository. 💻 Scan logsA new release of infisical is available: 0.41.90 -> 0.42.6
To update, run: sudo apt-get update && sudo apt-get install infisical
2:59PM INF scanning for exposed secrets...
2:59PM INF 41 commits scanned.
2:59PM INF scan completed in 339ms
2:59PM WRN leaks found: 6
🔎 Detected secrets in your GIT history
Warning The above table only displays the first 10 leaked secrets. 🐾 Secrets fingerprint2e1522054d3009edd4cc682e479341776b266eb0:src/mockData.ts:generic-api-key:505
2e1522054d3009edd4cc682e479341776b266eb0:src/pages/Integrations.tsx:generic-api-key:12
2e1522054d3009edd4cc682e479341776b266eb0:src/pages/RepositoryDetail.tsx:generic-api-key:124
2e1522054d3009edd4cc682e479341776b266eb0:src/pages/RepositoryDetail.tsx:generic-api-key:160
2e1522054d3009edd4cc682e479341776b266eb0:src/pages/RepositoryDetail.tsx:generic-api-key:178
2e1522054d3009edd4cc682e479341776b266eb0:src/pages/Settings.tsx:generic-api-key:127
Tip If you want to ignore these leaked secrets, add the above fingerprint content to a file named |
guibranco
deleted the
depfu/update/npm/eslint-plugin-react-refresh-0.4.22
branch
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-react-refresh (0.4.20 → 0.4.22) · Repo · Changelog
Release Notes
0.4.22
0.4.21
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 6 commits:
v0.4.22 [publish]Bump depsAdd viewport to Next.js config allowExportNames (#89)Fix publish permissionsUse OIDC [publish]Add Next config [publish] (#87)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.