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

fix(deps): update dependency replace-in-file to v8 #1332

Merged
merged 2 commits into from
Jul 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
replace-in-file 7.2.0 -> 8.1.0 age adoption passing confidence

Release Notes

adamreisnz/replace-in-file (replace-in-file)

v8.1.0

Compare Source

v8.0.3

Compare Source

v8.0.2

Compare Source

v8.0.1

Compare Source

v8.0.0

Compare Source

The package has been converted to an ES module and now requires Node 18 or higher. If you need support for Node 16 or below, please use version 7.x.x.

Breaking changes
  • Package has been converted to an ES module
  • No longer providing a default export. Use the named exports replaceInFile or replaceInFileSync instead.
  • The replace.sync syntax is no longer available. Use the named export replaceInFileSync instead.
  • The callback API has been removed for asynchronous replacements. Please use promises or async/await instead.
  • Configuration files provided to the CLI using the --configFile flag can now only be JSON.
  • To use a custom fs implementation, you must now specify fs config parameter for the async API, and fsSync for the sync API. For the asynchronous APIs, the provided fs must provide the readFile and writeFile methods. For the synchronous APIs, the provided fsSync must provide the readFileSync and writeFileSync methods.
  • If a cwd parameter is provided, it will no longer be prefixed to each path using basic string concatenation, but rather uses path.join() to ensure correct path concatenation.
New features

You can now specify a getTargetFile config param to modify the target file for saving the new file contents to. For example:

const options = {
  files: 'path/to/files/*.html',
  getTargetFile: source => `new/path/${source}`,
  from: 'foo',
  to: 'bar',
}

Configuration

📅 Schedule: Branch creation - "on sunday" in timezone Asia/Shanghai, 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 has been generated by Mend Renovate. View repository job log here.

@pkuhpc-review-bot pkuhpc-review-bot bot added the Code-ReviewRequested Code Review Requested label Jun 29, 2024
Copy link

changeset-bot bot commented Jun 29, 2024

⚠️ No Changeset found

Latest commit: 56ac664

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@pkuhpc-review-bot pkuhpc-review-bot bot requested a review from ddadaal June 29, 2024 19:01
@renovate renovate bot force-pushed the renovate/replace-in-file-8.x branch 3 times, most recently from 494e958 to 342beea Compare July 6, 2024 01:06
@renovate renovate bot force-pushed the renovate/replace-in-file-8.x branch from 342beea to 9d5fe8b Compare July 15, 2024 13:37
Copy link
Contributor Author

renovate bot commented Jul 15, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@ddadaal ddadaal merged commit 896c2d0 into master Jul 16, 2024
9 checks passed
@ddadaal ddadaal deleted the renovate/replace-in-file-8.x branch July 16, 2024 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code-ReviewRequested Code Review Requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant