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

Update all dependencies #173

Merged
merged 1 commit into from
Jan 18, 2023
Merged

Update all dependencies #173

merged 1 commit into from
Jan 18, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@​gauntface/logger 3.0.80 -> 3.0.81 age adoption passing confidence
@sentry/browser (source) 7.31.0 -> 7.31.1 age adoption passing confidence
@sentry/tracing (source) 7.31.0 -> 7.31.1 age adoption passing confidence
esbuild 0.17.1 -> 0.17.2 age adoption passing confidence

Release Notes

getsentry/sentry-javascript

v7.31.1

Compare Source

  • build(replay): Provide full browser+tracing+replay bundle (#​6793)
  • feat(nextjs): Disable NextJS perf monitoring when using otel (#​6820)
  • fix(nextjs): Add back browser field in package.json (#​6809)
  • fix(nextjs): Connect Edge API route errors to span (#​6806)
  • fix(nextjs): Correctly handle ts middleware files (#​6816)
evanw/esbuild

v0.17.2

Compare Source

  • Add onDispose to the plugin API (#​2140, #​2205)

    If your plugin wants to perform some cleanup after it's no longer going to be used, you can now use the onDispose API to register a callback for cleanup-related tasks. For example, if a plugin starts a long-running child process then it may want to terminate that process when the plugin is discarded. Previously there was no way to do this. Here's an example:

    let examplePlugin = {
      name: 'example',
      setup(build) {
        build.onDispose(() => {
          console.log('This plugin is no longer used')
        })
      },
    }

    These onDispose callbacks will be called after every build() call regardless of whether the build failed or not as well as after the first dispose() call on a given build context.


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot merged commit 176520d into main Jan 18, 2023
@renovate renovate bot deleted the renovate/all branch January 18, 2023 06:37
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.

None yet

0 participants