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(deps): replace dependency faker with @faker-js/faker ^5.5.3 - autoclosed #1054

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 17, 2024

This PR contains the following updates:

Package Type Update Change
faker devDependencies replacement ^6.6.6 -> ^5.5.3

This is a special PR that replaces faker with the community suggested minimal stable replacement version.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/faker-replacement branch from 31afcd7 to cba0260 Compare October 9, 2024 08:05
@renovate renovate bot force-pushed the renovate/faker-replacement branch from cba0260 to 374347b Compare October 22, 2024 13:37
@renovate renovate bot changed the title chore(deps): replace dependency faker with @faker-js/faker ^5.5.3 chore(deps): replace dependency faker with @faker-js/faker ^5.5.3 - autoclosed Oct 22, 2024
@renovate renovate bot closed this Oct 22, 2024
@renovate renovate bot deleted the renovate/faker-replacement branch October 22, 2024 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants