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.

Sign up for GitHub

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

Jump to bottom

Update all non-major dependencies #83

Merged
merged 1 commit into from
Dec 21, 2023
Merged

Update all non-major dependencies #83

merged 1 commit into from
Dec 21, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
lockFileMaintenance All locks refreshed age adoption passing confidence
@aws-cdk/aws-apigatewayv2-alpha (source) dependencies minor 2.113.0-alpha.0 -> 2.114.1-alpha.0 age adoption passing confidence
@aws-cdk/aws-apigatewayv2-integrations-alpha (source) dependencies minor 2.113.0-alpha.0 -> 2.114.1-alpha.0 age adoption passing confidence
@aws-sdk/client-secrets-manager (source) dependencies minor 3.465.0 -> 3.478.0 age adoption passing confidence
@trautonen/cdk-dns-validated-certificate dependencies patch 0.0.32 -> 0.0.35 age adoption passing confidence
@types/jest (source) devDependencies patch 29.5.10 -> 29.5.11 age adoption passing confidence
@types/luxon (source) devDependencies patch 3.3.6 -> 3.3.7 age adoption passing confidence
@types/node (source) devDependencies patch 20.10.2 -> 20.10.5 age adoption passing confidence
aws-cdk (source) devDependencies minor 2.113.0 -> 2.115.0 age adoption passing confidence
aws-cdk-lib (source) dependencies minor 2.113.0 -> 2.115.0 age adoption passing confidence
esbuild devDependencies patch 0.19.8 -> 0.19.10 age adoption passing confidence
ts-node (source) devDependencies patch 10.9.1 -> 10.9.2 age adoption passing confidence
typescript (source) devDependencies patch 5.3.2 -> 5.3.3 age adoption passing confidence

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/client-secrets-manager)

v3.478.0

Compare Source

Features

v3.477.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

v3.476.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

v3.474.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

v3.473.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

v3.470.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

v3.468.0

Compare Source

Note: Version bump only for package @​aws-sdk/client-secrets-manager

trautonen/cdk-dns-validated-certificate (@​trautonen/cdk-dns-validated-certificate)

v0.0.35

Compare Source

0.0.35 (2023-12-18)

v0.0.34

Compare Source

0.0.34 (2023-12-11)

v0.0.33

Compare Source

0.0.33 (2023-12-04)
aws/aws-cdk (aws-cdk)

v2.115.0

Compare Source

Features
Bug Fixes
Alpha modules (2.115.0-alpha.0)
⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES
  • scheduler: The typos in the Schedule and Group construct method names have been fixed, changing metricSentToDLQTrunacted to metricSentToDLQTruncated and metricAllSentToDLQTrunacted to metricAllSentToDLQTruncated.
  • redshift: Further updates of the Redshift table will fail for existing tables, if the table name is changed. Therefore, changing the table name for existing Redshift tables have been disabled.
Features
Bug Fixes

v2.114.1

Compare Source

Bug Fixes
Alpha modules (2.114.1-alpha.0)

v2.114.0

Compare Source

Features
Bug Fixes
Alpha modules (2.114.0-alpha.0)
Features
evanw/esbuild (esbuild)

v0.19.10

Compare Source

  • Fix glob imports in TypeScript files (#​3319)

    This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

  • Fix require() glob imports with bundling disabled (#​3546)

    Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

  • Fix a panic when transforming optional chaining with define (#​3551, #​3554)

    This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

    // Original code
console.log(process?.env.SHELL)

// Old output (with --define:process.env={})
/* panic: Internal error (while parsing "<stdin>") */

// New output (with --define:process.env={})
var define_process_env_default = {};
console.log(define_process_env_default.SHELL);

    This fix was contributed by @​hi-ogawa.

  • Work around a bug in node's CommonJS export name detector (#​3544)

    The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

    When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

    // confuseNode.js
exports.confuseNode = function(exports) {
  // If this local is called "exports", node incorrectly
  // thinks this file has an export called "notAnExport".
  exports.notAnExport = function() {
  };
};

    You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

    $ node -e 'import("./confuseNode.js").then(console.log)'
[Module: null prototype] {
  confuseNode: [Function (anonymous)],
  default: { confuseNode: [Function (anonymous)] },
  notAnExport: undefined
}

    To avoid this, esbuild will now rename local variables that use the names exports and module when generating CommonJS output for the node platform.

  • Fix the return value of esbuild's super() shim (#​3538)

    Some people write constructor methods that use the return value of super() instead of using this. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value of super() into undefined. With this release, the return value of super() will now be this instead:

    // Original code
class Foo extends Object {
  field
  constructor() {
    console.log(typeof super())
  }
}
new Foo

// Old output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
    };
    console.log(typeof __super());
  }
}
new Foo();

// New output (with --target=es6)
class Foo extends Object {
  constructor() {
    var __super = (...args) => {
      super(...args);
      __publicField(this, "field");
      return this;
    };
    console.log(typeof __super());
  }
}
new Foo();

  • Terminate the Go GC when esbuild's stop() API is called (#​3552)

    If you use esbuild with WebAssembly and pass the worker: false flag to esbuild.initialize(), then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test calls esbuild.stop() to clean up esbuild's resources, Deno may complain that a setTimeout() call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally calling esbuild.stop() will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker with worker: false.

    With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling clearTimeout() on these pending timeouts.

  • Apply /* @&#8203;__NO_SIDE_EFFECTS__ */ on tagged template literals (#​3511)

    Tagged template literals that reference functions annotated with a @__NO_SIDE_EFFECTS__ comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:

    // Original code
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
html`<a>remove</a>`
x = html`<b>keep</b>`

// Old output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
html`<a>remove</a>`;
x = html`<b>keep</b>`;

// New output (with --tree-shaking=true)
const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
x = html`<b>keep</b>`;

    Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using @__PURE__ annotations instead of this feature, as they have wider tooling support. The drawback of course is that @__PURE__ annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the @__PURE__ annotation to.

  • Publish builds for IBM AIX PowerPC 64-bit (#​3549)

    This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with npm install esbuild. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.

v0.19.9

Compare Source

  • Add support for transforming new CSS gradient syntax for older browsers

    The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in Mozilla's blog post about new CSS gradient features.

    With this release, esbuild will now automatically transform this syntax for older browsers in the target list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax:

    /* Original code */
.rainbow-gradient {
  width: 100px;
  height: 100px;
  background: linear-gradient(in hsl longer hue, #&#8203;7ff, #&#8203;77f);
}

/* New output (with --target=chrome99) */
.rainbow-gradient {
  width: 100px;
  height: 100px;
  background:
    linear-gradient(
      #&#8203;77ffff,
      #&#8203;77ffaa 12.5%,
      #&#8203;77ff80 18.75%,
      #&#8203;84ff77 21.88%,
      #&#8203;99ff77 25%,
      #eeff77 37.5%,
      #fffb77 40.62%,
      #ffe577 43.75%,
      #ffbb77 50%,
      #ff9077 56.25%,
      #ff7b77 59.38%,
      #ff7788 62.5%,
      #ff77dd 75%,
      #ff77f2 78.12%,
      #f777ff 81.25%,
      #cc77ff 87.5%,
      #&#8203;7777ff);
}

    You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate:

    /* Original code */
.stripes {
  width: 100px;
  height: 100px;
  background: linear-gradient(#e65 33%, #ff2 33% 67%, #&#8203;99e 67%);
}
.glow {
  width: 100px;
  height: 100px;
  background: radial-gradient(white 10%, 20%, black);
}

/* New output (with --target=chrome33) */
.stripes {
  width: 100px;
  height: 100px;
  background:
    linear-gradient(
      #e65 33%,
      #ff2 33%,
      #ff2 67%,
      #&#8203;99e 67%);
}
.glow {
  width: 100px;
  height: 100px;
  background:
    radial-gradient(
      #ffffff 10%,
      #aaaaaa 12.81%,
      #&#8203;959595 15.62%,
      #&#8203;7b7b7b 21.25%,
      #&#8203;5a5a5a 32.5%,
      #&#8203;444444 43.75%,
      #&#8203;323232 55%,
      #&#8203;161616 77.5%,
      #&#8203;000000);
}

    You can see visual examples of these new syntax features by looking at esbuild's gradient transformation tests.

    If necessary, esbuild will construct a new gradient that approximates the original gradient by recursively splitting the interval in between color stops until the approximation error is within a small threshold. That is why the above output CSS contains many more color stops than the input CSS.

    Note that esbuild deliberately replaces the original gradient with the approximation instead of inserting the approximation before the original gradient as a fallback. The latest version of Firefox has multiple gradient rendering bugs (including incorrect interpolation of partially-transparent colors and interpolating non-sRGB colors using the incorrect color space). If esbuild didn't replace the original gradient, then Firefox would use the original gradient instead of the fallback the appearance would be incorrect in Firefox. In other words, the latest version of Firefox supports modern gradient syntax but interprets it incorrectly.

  • Add support for color(), lab(), lch(), oklab(), oklch(), and hwb() in CSS

    CSS has recently added lots of new ways of specifying colors. You can read more about this in Chrome's blog post about CSS color spaces.

    This release adds support for minifying colors that use the color(), lab(), lch(), oklab(), oklch(), or hwb() syntax and/or transforming these colors for browsers that don't support it yet:

    /* Original code */
div {
  color: hwb(90deg 20% 40%);
  background: color(display-p3 1 0 0);
}

/* New output (with --target=chrome99) */
div {
  color: #&#8203;669933;
  background: #ff0f0e;
  background: color(display-p3 1 0 0);
}

    As you can see, colors outside of the sRGB color space such as color(display-p3 1 0 0) are mapped back into the sRGB gamut and inserted as a fallback for browsers that don't support the new color syntax.

  • Allow empty type parameter lists in certain cases (#​3512)

    TypeScript allows interface declarations and type aliases to have empty type parameter lists. Previously esbuild didn't handle this edge case but with this release, esbuild will now parse this syntax:

    interface Foo<> {}
type Bar<> = {}

    This fix was contributed by @​magic-akari.

TypeStrong/ts-node (ts-node)

v10.9.2: Fix tsconfig.json file not found

Compare Source

Fixed

Microsoft/TypeScript (typescript)

v5.3.3: TypeScript 5.3.3

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Configuration

📅 Schedule: Branch creation - "before 5am on sunday" (UTC), 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.

👻 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 added the maintenance label Dec 3, 2023
mergify[bot]
mergify bot previously approved these changes Dec 3, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 3, 2023
View reviewed changes
@renovate renovate bot changed the title Update Update all non-major dependencies Dec 3, 2023
mergify[bot]
mergify bot previously approved these changes Dec 3, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 4, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 4, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 5, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 6, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 6, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 6, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 6, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 13, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 14, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 14, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 18, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 18, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 19, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 19, 2023
View reviewed changes
mergify[bot]
mergify bot previously approved these changes Dec 20, 2023
View reviewed changes
@SvenKirschbaum SvenKirschbaum merged commit 279056a into master Dec 21, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mergify Mergify mergify approved these changes

Assignees
No one assigned
Labels
maintenance
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@SvenKirschbaum