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 #191

Merged
merged 1 commit into from
Feb 14, 2023
Merged

Update all dependencies #191

merged 1 commit into from
Feb 14, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 13, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@sentry/browser (source) 7.37.1 -> 7.37.2 age adoption passing confidence
@sentry/tracing (source) 7.37.1 -> 7.37.2 age adoption passing confidence
@typescript-eslint/eslint-plugin 5.51.0 -> 5.52.0 age adoption passing confidence
@typescript-eslint/parser 5.51.0 -> 5.52.0 age adoption passing confidence
esbuild 0.17.7 -> 0.17.8 age adoption passing confidence

Release Notes

getsentry/sentry-javascript

v7.37.2

Compare Source

This release includes changes and fixes around text masking and blocking in Replay's rrweb dependency. See versions 1.102.0 and 1.103.0.

  • feat: Check blockSelector for blocking elements as well
  • feat: With maskAllText, mask the attributes: placeholder, title, aria-label
  • feat: fix masking on textarea
  • feat: Add maskAllText option

SDK Changes:

  • fix(replay): Fix svgs not getting unblocked (#​7132)
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.52.0

Compare Source

Bug Fixes
  • eslint-plugin: [no-import-type-side-effects] correctly ignore zero-specifier imports (#​6444) (d5a6688)
  • eslint-plugin: [no-unnecessary-condition] account for optional chaining on potentially void values (#​6432) (e1d9c67), closes #​5255
  • eslint-plugin: [no-unnecessary-condition] fix false positive when checking indexed access types (#​6452) (d569924)
  • eslint-plugin: fix key-spacing when type starts on next line (#​6412) (3eb2eed)
Features
  • eslint-plugin: [block-spacing] extending base rule for TS related blocks (#​6195) (b2db3f5)
  • eslint-plugin: [explicit-function-return-type] add allowFunctionsWithoutTypeParameters option (#​6105) (113640e)
  • eslint-plugin: [explicit-function-return-type] add allowIIFEs option (#​6237) (a1b3f7b)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.52.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

evanw/esbuild

v0.17.8

Compare Source

  • Fix a minification bug with non-ASCII identifiers (#​2910)

    This release fixes a bug with esbuild where non-ASCII identifiers followed by a keyword were incorrectly not separated by a space. This bug affected both the in and instanceof keywords. Here's an example of the fix:

    // Original code
    π in a
    
    // Old output (with --minify --charset=utf8)
    πin a;
    
    // New output (with --minify --charset=utf8)
    π in a;
  • Fix a regression with esbuild's WebAssembly API in version 0.17.6 (#​2911)

    Version 0.17.6 of esbuild updated the Go toolchain to version 1.20.0. This had the unfortunate side effect of increasing the amount of stack space that esbuild uses (presumably due to some changes to Go's WebAssembly implementation) which could cause esbuild's WebAssembly-based API to crash with a stack overflow in cases where it previously didn't crash. One such case is the package grapheme-splitter which contains code that looks like this:

    if (
      (0x0300 <= code && code <= 0x036F) ||
      (0x0483 <= code && code <= 0x0487) ||
      (0x0488 <= code && code <= 0x0489) ||
      (0x0591 <= code && code <= 0x05BD) ||
      // ... many hundreds of lines later ...
    ) {
      return;
    }

    This edge case involves a chain of binary operators that results in an AST over 400 nodes deep. Normally this wouldn't be a problem because Go has growable call stacks, so the call stack would just grow to be as large as needed. However, WebAssembly byte code deliberately doesn't expose the ability to manipulate the stack pointer, so Go's WebAssembly translation is forced to use the fixed-size WebAssembly call stack. So esbuild's WebAssembly implementation is vulnerable to stack overflow in cases like these.

    It's not unreasonable for this to cause a stack overflow, and for esbuild's answer to this problem to be "don't write code like this." That's how many other AST-manipulation tools handle this problem. However, it's possible to implement AST traversal using iteration instead of recursion to work around limited call stack space. This version of esbuild implements this code transformation for esbuild's JavaScript parser and printer, so esbuild's WebAssembly implementation is now able to process the grapheme-splitter package (at least when compiled with Go 1.20.0 and run with node's WebAssembly implementation).


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 31101c4 into main Feb 14, 2023
@renovate renovate bot deleted the renovate/all branch February 14, 2023 04: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.

None yet

0 participants