fix(deps): update all non-major dependencies #35

renovate · 2023-11-13T00:16:13Z

This PR contains the following updates:

Package	Change	Type	Update
@aws-sdk/client-ses (source)	`3.433.0` -> `3.454.0`	dependencies	minor
@fastify/cors	`8.4.0` -> `8.4.1`	dependencies	patch
@fastify/jwt	`7.2.2` -> `7.2.4`	dependencies	patch
@fastify/oauth2	`7.5.0` -> `7.7.0`	devDependencies	minor
@fastify/oauth2	`7.5.0` -> `7.7.0`	dependencies	minor
@sxzz/eslint-config	`3.7.0` -> `3.7.4`	devDependencies	patch
@types/jsonwebtoken (source)	`9.0.4` -> `9.0.5`	devDependencies	patch
@types/lodash-es (source)	`4.17.10` -> `4.17.12`	devDependencies	patch
@types/node (source)	`20.8.7` -> `20.10.0`	devDependencies	minor
bullmq (source)	`4.12.5` -> `4.14.2`	dependencies	minor
esbuild	`0.19.5` -> `0.19.7`	devDependencies	patch
esbuild-plugin-pino	`2.0.2` -> `2.1.0`	devDependencies	minor
eslint (source)	`8.52.0` -> `8.54.0`	devDependencies	minor
lint-staged	`15.0.2` -> `15.1.0`	devDependencies	minor
mongoose (source)	`7.6.3` -> `7.6.5`	dependencies	patch
mongoose (source)	`7.6.3` -> `7.6.5`	devDependencies	patch
node	`20.8.0-alpine` -> `20.10.0-alpine`	final	minor
node (source)	`20.9.0` -> `20.10.0`		minor
pino (source)	`8.16.1` -> `8.16.2`	dependencies	patch
pnpm (source)	`8.10.0` -> `8.10.5`	packageManager	patch
prettier (source)	`3.0.3` -> `3.1.0`	devDependencies	minor
remeda	`1.27.1` -> `1.29.0`	dependencies	minor
typescript (source)	`5.2.2` -> `5.3.2`	devDependencies	minor

Release Notes

aws/aws-sdk-js-v3 (@aws-sdk/client-ses)

`v3.454.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.451.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.450.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.449.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.445.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.441.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.438.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.437.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.436.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

`v3.435.0`

Compare Source

Note: Version bump only for package @aws-sdk/client-ses

fastify/fastify-cors (@fastify/cors)

fastify/fastify-jwt (@fastify/jwt)

`v7.2.4`

Compare Source

📚 PR:

Bump fast-jwt

`v7.2.3`

Compare Source

What's Changed

Added missing comma in cookie example by @sakerhetspolisen in https://github.com/fastify/fastify-jwt/pull/311
chore(package): explicitly declare js module type by @Fdawgs in https://github.com/fastify/fastify-jwt/pull/312
types: add key option to sign and verify by @KirillTregubov in https://github.com/fastify/fastify-jwt/pull/314

New Contributors

@sakerhetspolisen made their first contribution in https://github.com/fastify/fastify-jwt/pull/311
@KirillTregubov made their first contribution in https://github.com/fastify/fastify-jwt/pull/314

Full Changelog: fastify/fastify-jwt@v7.2.2...v7.2.3

fastify/fastify-oauth2 (@fastify/oauth2)

`v7.7.0`

Compare Source

What's Changed

Feature: OpenID Connect Discovery support by @big-kahuna-burger in https://github.com/fastify/fastify-oauth2/pull/242

Full Changelog: fastify/fastify-oauth2@v7.6.0...v7.7.0

`v7.6.0`

Compare Source

What's Changed

chore: add .gitattributes file by @Fdawgs in https://github.com/fastify/fastify-oauth2/pull/233
chore(examples): add missing use strict directives by @Fdawgs in https://github.com/fastify/fastify-oauth2/pull/234
chore(package): explicitly declare js module type by @Fdawgs in https://github.com/fastify/fastify-oauth2/pull/235
feat: implement PKCE extension for Authorization Code Grant (RFC 7636) by @big-kahuna-burger in https://github.com/fastify/fastify-oauth2/pull/240

New Contributors

@big-kahuna-burger made their first contribution in https://github.com/fastify/fastify-oauth2/pull/240

Full Changelog: fastify/fastify-oauth2@v7.5.0...v7.6.0

sxzz/eslint-config (@sxzz/eslint-config)

`v3.7.4`

Compare Source

🚀 Features

Detect @unocss/nuxt - by @sxzz (c68ff)

View changes on GitHub

`v3.7.3`

Compare Source

🚀 Features

Enable vue&unocss by env - by @sxzz (8d6de)

View changes on GitHub

`v3.7.2`

Compare Source

🐞 Bug Fixes

Markdown preset & add presetJsonc - by @sxzz (25087)

View changes on GitHub

`v3.7.1`

Compare Source

🐞 Bug Fixes

Disable vue/one-component-per-file - by @sxzz (38b19)
deps: Update dependency eslint-plugin-unicorn to v49 - by @renovate[bot] inhttps://github.com/sxzz/eslint-config/issues/422 (42944)

View changes on GitHub

taskforcesh/bullmq (bullmq)

`v4.14.2`

Compare Source

Bug Fixes

worker: should cap update progress events (2cab9e9)

`v4.14.1`

Compare Source

Bug Fixes

worker: do not wait for slow jobs fixes #2290 (568d758)

`v4.14.0`

Compare Source

Features

worker: better handling of concurrency when fetching jobs (#2242) (d2e2035)

`v4.13.3`

Compare Source

Bug Fixes

utils: use EventEmitter as a type instead of a namespace (#2283) (41c9d1d)

`v4.13.2`

Compare Source

Bug Fixes

backoff: fix builtin backoff type (#2265) [python] (76959eb)
job: set delay value on current job instance when it is retried (#2266) (python) (76e075f)

`v4.13.1`

Compare Source

Bug Fixes

connection: better handling of attached listeners (02474ad)
connection: move redis instance check to queue base (13a339a)

`v4.13.0`

Compare Source

Features

queue: improve clean to work iteratively (#2260) (0cfa66f)

`v4.12.10`

Compare Source

Bug Fixes

update delay job property when moving to delayed set (#2261) (69ece08)

`v4.12.9`

Compare Source

Bug Fixes

add-job: trim events when waiting-children event is published (#2262) (python) (198bf05)

`v4.12.8`

Compare Source

Bug Fixes

worker: keep extending locks while closing workers (#2259) (c4d12ea)

`v4.12.7`

Compare Source

Performance Improvements

redis-connection: check redis version greater or equal than v6 only once (#2252) (a09b15a)

`v4.12.6`

Compare Source

Bug Fixes

sandbox: do not return empty object result when it is undefined (#2247) (308db7f)

evanw/esbuild (esbuild)

`v0.19.7`

Compare Source

Add support for bundling code that uses import attributes (#3384)

JavaScript is gaining new syntax for associating a map of string key-value pairs with individual ESM imports. The proposal is still a work in progress and is still undergoing significant changes before being finalized. However, the first iteration has already been shipping in Chromium-based browsers for a while, and the second iteration has landed in V8 and is now shipping in node, so it makes sense for esbuild to support it. Here are the two major iterations of this proposal (so far):
1. Import assertions (deprecated, will not be standardized)
  - Uses the assert keyword
  - Does not affect module resolution
  - Causes an error if the assertion fails
  - Shipping in Chrome 91+ (and in esbuild 0.11.22+)
2. Import attributes (currently set to become standardized)
  - Uses the with keyword
  - Affects module resolution
  - Unknown attributes cause an error
  - Shipping in node 21+
You can already use esbuild to bundle code that uses import assertions (the first iteration). However, this feature is mostly useless for bundlers because import assertions are not allowed to affect module resolution. It's basically only useful as an annotation on external imports, which esbuild will then preserve in the output for use in a browser (which would otherwise refuse to load certain imports).

With this release, esbuild now supports bundling code that uses import attributes (the second iteration). This is much more useful for bundlers because they are allowed to affect module resolution, which means the key-value pairs can be provided to plugins. Here's an example, which uses esbuild's built-in support for the upcoming JSON module standard:
```
// On static imports
import foo from './package.json' with { type: 'json' }
console.log(foo)

// On dynamic imports
const bar = await import('./package.json', { with: { type: 'json' } })
console.log(bar)
```
One important consequence of the change in semantics between import assertions and import attributes is that two imports with identical paths but different import attributes are now considered to be different modules. This is because the import attributes are provided to the loader, which might then use those attributes during loading. For example, you could imagine an image loader that produces an image of a different size depending on the import attributes.

Import attributes are now reported in the metafile and are now provided to on-load plugins as a map in the with property. For example, here's an esbuild plugin that turns all imports with a type import attribute equal to 'cheese' into a module that exports the cheese emoji:
```
const cheesePlugin = {
  name: 'cheese',
  setup(build) {
    build.onLoad({ filter: /.*/ }, args => {
      if (args.with.type === 'cheese') return {
        contents: `export default "🧀"`,
      }
    })
  }
}

require('esbuild').build({
  bundle: true,
  write: false,
  stdin: {
    contents: `
      import foo from 'data:text/javascript,' with { type: 'cheese' }
      console.log(foo)
    `,
  },
  plugins: [cheesePlugin],
}).then(result => {
  const code = new Function(result.outputFiles[0].text)
  code()
})
```
Warning: It's possible that the second iteration of this feature may change significantly again even though it's already shipping in real JavaScript VMs (since it has already happened once before). In that case, esbuild may end up adjusting its implementation to match the eventual standard behavior. So keep in mind that by using this, you are using an unstable upcoming JavaScript feature that may undergo breaking changes in the future.
Adjust TypeScript experimental decorator behavior (#3230, #3326, #3394)

With this release, esbuild will now allow TypeScript experimental decorators to access both static class properties and #private class names. For example:
```
const check =
  <T,>(a: T, b: T): PropertyDecorator =>
    () => console.log(a === b)

async function test() {
  class Foo {
    static #foo = 1
    static bar = 1 + Foo.#foo
    @&#8203;check(Foo.#foo, 1) a: any
    @&#8203;check(Foo.bar, await Promise.resolve(2)) b: any
  }
}

test().then(() => console.log('pass'))
```
This will now print true true pass when compiled by esbuild. Previously esbuild evaluated TypeScript decorators outside of the class body, so it didn't allow decorators to access Foo or #foo. Now esbuild does something different, although it's hard to concisely explain exactly what esbuild is doing now (see the background section below for more information).

Note that TypeScript's experimental decorator support is currently buggy: TypeScript's compiler passes this test if only the first @check is present or if only the second @check is present, but TypeScript's compiler fails this test if both checks are present together. I haven't changed esbuild to match TypeScript's behavior exactly here because I'm waiting for TypeScript to fix these bugs instead.

Some background: TypeScript experimental decorators don't have consistent semantics regarding the context that the decorators are evaluated in. For example, TypeScript will let you use await within a decorator, which implies that the decorator runs outside the class body (since await isn't supported inside a class body), but TypeScript will also let you use #private names, which implies that the decorator runs inside the class body (since #private names are only supported inside a class body). The value of this in a decorator is also buggy (the run-time value of this changes if any decorator in the class uses a #private name but the type of this doesn't change, leading to the type checker no longer matching reality). These inconsistent semantics make it hard for esbuild to implement this feature as decorator evaluation happens in some superposition of both inside and outside the class body that is particular to the internal implementation details of the TypeScript compiler.
Forbid --keep-names when targeting old browsers (#3477)

The --keep-names setting needs to be able to assign to the name property on functions and classes. However, before ES6 this property was non-configurable, and attempting to assign to it would throw an error. So with this release, esbuild will no longer allow you to enable this setting while also targeting a really old browser.

`v0.19.6`

Compare Source

Fix a constant folding bug with bigint equality

This release fixes a bug where esbuild incorrectly checked for bigint equality by checking the equality of the bigint literal text. This is correct if the bigint doesn't have a radix because bigint literals without a radix are always in canonical form (since leading zeros are not allowed). However, this is incorrect if the bigint has a radix (e.g. 0x123n) because the canonical form is not enforced when a radix is present.
```
// Original code
console.log(!!0n, !!1n, 123n === 123n)
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn)

// Old output
console.log(false, true, true);
console.log(true, true, false);

// New output
console.log(false, true, true);
console.log(!!0x0n, !!0x1n, 123n === 0x7Bn);
```

Add some improvements to the JavaScript minifier

This release adds more cases to the JavaScript minifier, including support for inlining String.fromCharCode and String.prototype.charCodeAt when possible:

// Original code
document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) && console.log(String.fromCharCode(55358, 56768))

// Old output (with --minify)
document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768));

// New output (with --minify)
document.onkeydown=o=>o.keyCode===65&&console.log("🧀");

In addition, immediately-invoked function expressions (IIFEs) that return a single expression are now inlined when minifying. This makes it possible to use IIFEs in combination with @__PURE__ annotations to annotate arbitrary expressions as side-effect free without the IIFE wrapper impacting code size. For example:

// Original code
const sideEffectFreeOffset = /* @&#8203;__PURE__ */ (() => computeSomething())()
use(sideEffectFreeOffset)

// Old output (with --minify)
const e=(()=>computeSomething())();use(e);

// New output (with --minify)
const e=computeSomething();use(e);

Automatically prefix the mask-composite CSS property for WebKit (#3493)

The mask-composite property will now be prefixed as -webkit-mask-composite for older WebKit-based browsers. In addition to prefixing the property name, handling older browsers also requires rewriting the values since WebKit uses non-standard names for the mask composite modes:
```
/* Original code */
div {
  mask-composite: add, subtract, intersect, exclude;
}

/* New output (with --target=chrome100) */
div {
  -webkit-mask-composite:
    source-over,
    source-out,
    source-in,
    xor;
  mask-composite:
    add,
    subtract,
    intersect,
    exclude;
}
```
Avoid referencing this from JSX elements in derived class constructors (#3454)

When you enable --jsx=automatic and --jsx-dev, the JSX transform is supposed to insert this as the last argument to the jsxDEV function. I'm not sure exactly why this is and I can't find any specification for it, but in any case this causes the generated code to crash when you use a JSX element in a derived class constructor before the call to super() as this is not allowed to be accessed at that point. For example
```
// Original code
class ChildComponent extends ParentComponent {
  constructor() {
    super(<div />)
  }
}

// Problematic output (with --loader=jsx --jsx=automatic --jsx-dev)
import { jsxDEV } from "react/jsx-dev-runtime";
class ChildComponent extends ParentComponent {
  constructor() {
    super(/* @&#8203;__PURE__ */ jsxDEV("div", {}, void 0, false, {
      fileName: "<stdin>",
      lineNumber: 3,
      columnNumber: 15
    }, this)); // The reference to "this" crashes here
  }
}
```
The TypeScript compiler doesn't handle this at all while the Babel compiler just omits this for the entire constructor (even after the call to super()). There seems to be no specification so I can't be sure that this change doesn't break anything important. But given that Babel is pretty loose with this and TypeScript doesn't handle this at all, I'm guessing this value isn't too important. React's blog post seems to indicate that this value was intended to be used for a React-specific migration warning at some point, so it could even be that this value is irrelevant now. Anyway the crash in this case should now be fixed.
Allow package subpath imports to map to node built-ins (#3485)

You are now able to use a subpath import in your package to resolve to a node built-in module. For example, with a package.json file like this:
```
{
  "type": "module",
  "imports": {
    "#stream": {
      "node": "stream",
      "default": "./stub.js"
    }
  }
}
```
You can now import from node's stream module like this:
```
import * as stream from '#stream';
console.log(Object.keys(stream));
```
This will import from node's stream module when the platform is node and from ./stub.js otherwise.
No longer throw an error when a Symbol is missing (#3453)

Certain JavaScript syntax features use special properties on the global Symbol object. For example, the asynchronous iteration syntax uses Symbol.asyncIterator. Previously esbuild's generated code for older browsers required this symbol to be polyfilled. However, starting with this release esbuild will use Symbol.for() to construct these symbols if they are missing instead of throwing an error about a missing polyfill. This means your code no longer needs to include a polyfill for missing symbols as long as your code also uses Symbol.for() for missing symbols.
Parse upcoming changes to TypeScript syntax (#3490, #3491)

With this release, you can now use from as the name of a default type-only import in TypeScript code, as well as of as the name of an await using loop iteration variable:
```
import type from from 'from'
for (await using of of of) ;
```
This matches similar changes in the TypeScript compiler (#56376 and #55555) which will start allowing this syntax in an upcoming version of TypeScript. Please never actually write code like this.

The type-only import syntax change was contributed by @magic-akari.

davipon/esbuild-plugin-pino (esbuild-plugin-pino)

`v2.1.0`

Compare Source

🔨 Build System

deps-dev: bump postcss from 8.4.27 to 8.4.31 (#111) (3f112a0)

🚚 Chores

deps: update all non-major dependencies (4e4f107)
deps: update all non-major dependencies (5f0013d)
deps: update all non-major dependencies (e661f93)

✨ Features

respect outExtension option from esbuild (#115) (90ed134)

2.0.2 (2023-10-04)

🚚 Chores

deps: update all major dependencies (#105) (02c374e)
deps: update all non-major dependencies (6ef76a2)
deps: update all non-major dependencies (f889c8b)
deps: update all non-major dependencies (7cb2a7b)
deps: update all non-major dependencies (68e971f)
deps: update all non-major dependencies (944b6d4)
deps: update all non-major dependencies (ef4fe3e)
deps: update all non-major dependencies (b6b2404)
deps: update dependency execa to v8 (#101) (3035684)

🔨 Build System

deps: bump actions/checkout from 3 to 4 (#108) (c7daaa5)

✨ Features

support absolute dist paths and use absWorkingDir is present (#110) (30f274b)

2.0.1 (2023-08-18)

🔨 Build System

deps-dev: bump vite from 4.2.1 to 4.4.8 (#94) (bc86bba)

🚚 Chores

deps: update all major dependencies (#91) (21d71eb)
deps: update all major dependencies to v3 (#89) (a29fb12)
deps: update all non-major dependencies (3bb2711)
deps: update all non-major dependencies (376040f)
deps: update all non-major dependencies (5cb9ef4)
deps: update all non-major dependencies (5de5e4a)
deps: update all non-major dependencies (1488fd1)
deps: update all non-major dependencies (636f12b)
deps: update all non-major dependencies (51e0a0a)
deps: update all non-major dependencies (dc8a900)
deps: update all non-major dependencies (a698abe)
deps: update all non-major dependencies (734b401)
deps: update all non-major dependencies (d2e5b73)
deps: update all non-major dependencies (318a62e)
deps: update all non-major dependencies (#83) (ec5f47d)
deps: update dependency esbuild to v0.17.17 (7c10f62)
deps: update dependency esbuild to v0.19.2 (c50a3b9)
deps: update dependency eslint-config-prettier to v9 (#96) (55ac32c)

eslint/eslint (eslint)

`v8.54.0`

Compare Source

Features

a7a883b feat: for-direction rule add check for condition in reverse order (#17755) (Angelo Annunziata)
1452dc9 feat: Add suggestions to no-console (#17680) (Joel Mathew Koshy)
21ebf8a feat: update no-array-constructor rule (#17711) (Francesco Trotta)

Bug Fixes

98926e6 fix: Ensure that extra data is not accidentally stored in the cache file (#17760) (Milos Djermanovic)
e8cf9f6 fix: Make dark scroll bar in dark theme (#17753) (Pavel)
3cbeaad fix: Use cwd constructor option as config basePath in Linter (#17705) (Milos Djermanovic)

Documentation

becfdd3 docs: Make clear when rules are removed (#17728) (Nicholas C. Zakas)
05d6e99 docs: update "Submit a Pull Request" page (#17712) (Francesco Trotta)
eb2279e docs: display info about deprecated rules (#17749) (Percy Ma)
d245326 docs: Correct working in migrating plugin docs (#17722) (Filip Tammergård)

Chores

d644de9 chore: upgrade @eslint/js @8.54.0 (#17773) (Milos Djermanovic)
1e6e314 chore: package.json update for @eslint/js release (Jenkins)
[6fb8805](https://togithub.com/eslint/eslint/commit/6fb8805310afe7476d6c404f172177a6d15fcf

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (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 bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from fb81bcf to 89f6a46 Compare November 20, 2023 02:43

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from bfd31ff to 7ba0be9 Compare November 23, 2023 01:13

fix(deps): update all non-major dependencies

32d19bf

renovate bot force-pushed the renovate/all-minor-patch branch from 7ba0be9 to 32d19bf Compare November 24, 2023 13:28

Joabesv self-requested a review November 24, 2023 13:28

Joabesv approved these changes Nov 24, 2023

View reviewed changes

Joabesv merged commit 82e2cb7 into main Nov 24, 2023
1 check passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update all non-major dependencies #35

fix(deps): update all non-major dependencies #35

renovate bot commented Nov 13, 2023 •

edited

Loading

fix(deps): update all non-major dependencies #35

fix(deps): update all non-major dependencies #35

Conversation

renovate bot commented Nov 13, 2023 • edited Loading

Release Notes

What's Changed

New Contributors

What's Changed

New Contributors

What's Changed

What's Changed

New Contributors

🚀 Features

🚀 Features

🐞 Bug Fixes

🐞 Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Performance Improvements

Bug Fixes

🔨 Build System

🚚 Chores

✨ Features

2.0.2 (2023-10-04)

🚚 Chores

🔨 Build System

✨ Features

2.0.1 (2023-08-18)

🔨 Build System

🚚 Chores

Features

Bug Fixes

Documentation

Chores

Configuration

renovate bot commented Nov 13, 2023 •

edited

Loading