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 non-major dependencies #1

Merged
merged 1 commit into from
Mar 2, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 12, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@forestadmin/agent ^1.8.0 -> ^1.8.3 age adoption passing confidence
@forestadmin/datasource-customizer ^1.5.11 -> ^1.5.12 age adoption passing confidence
@nuxt/kit ^3.2.0 -> ^3.2.3 age adoption passing confidence
@nuxt/schema ^3.2.0 -> ^3.2.3 age adoption passing confidence
@nuxt/test-utils ^3.2.0 -> ^3.2.3 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.50.0 -> ^5.54.0 age adoption passing confidence
@typescript-eslint/parser ^5.50.0 -> ^5.54.0 age adoption passing confidence
eslint (source) ^8.34.0 -> ^8.35.0 age adoption passing confidence
nuxt ^3.2.0 -> ^3.2.3 age adoption passing confidence
pnpm (source) 7.26.3 -> 7.28.0 age adoption passing confidence
prettier (source) ^2.8.3 -> ^2.8.4 age adoption passing confidence
vitest ^0.28.4 -> ^0.29.2 age adoption passing confidence

Release Notes

ForestAdmin/agent-nodejs (@​forestadmin/agent)

v1.8.3

Compare Source

Dependencies

v1.8.2

Compare Source

Bug Fixes
  • schema: must be sorted by collection name to avoid conflict (#​626) (0fc7ba0)

v1.8.1

Compare Source

Bug Fixes
  • schema: use forest-express schema format for CLI compatibility (#​622) (4ac8bcb)
Dependencies
ForestAdmin/agent-nodejs (@​forestadmin/datasource-customizer)

v1.5.12

Compare Source

nuxt/nuxt

v3.2.3

Compare Source

3.2.3 is a patch release with bug fixes and performance improvements.

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Don't update manifest in dev mode (#​19315)
🩹 Fixes
  • cli: Restart nuxt when distDir is unlinked (#​19131)
  • vite: Normalize path emitted by vite watcher (#​19179)
  • nuxt: Prefetch object-syntax routes with <NuxtLink> (#​19144)
  • webpack: Use default export from webpack (#​19166)
  • nuxt: Preserve (re)named imports in meta (#​19192)
  • nuxt: Log errors thrown when booting the nuxt app (#​19187)
  • nuxt: Preserve explicit rel attribute on internal link (#​19309)
  • nuxt: Compatible route object for custom external routes (#​19261)
  • vite: Handle non-iterable noExternal option (#​19256)
📖 Documentation
🏡 Chore
🤖 CI
❤️ Contributors

v3.2.2

Compare Source

3.2.1 is a patch release with (lots of) bug fixes and performance improvements since last week's minor release.
3.2.2 was a swiftly following release to patch an issue with nuxi init

👀 Highlights

As a patch release, there are mostly bug fixes and performance improvements in the changelog. (Nevertheless, it's always worth reading through!) But one point of note is an experimental reload strategy when chunk errors are encountered. We're hoping to finalise the API and land it in v3.3 (our next feature release) with https://github.com/nuxt/nuxt/pull/19086, but you can test out an experimental version with the following config:

export default defineNuxtConfig({
  experimental: {
    emitRouteChunkError: 'reload'
  }
})

With this strategy, your app will hard reload on route changes if there's a chunk error. More info at https://github.com/nuxt/nuxt/pull/19038.

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: Add experimental app:chunkError hook and reload strategy (#​19038)
🔥 Performance
  • nuxt: Allow tree-shaking empty meta from build (#​19032)
  • nuxt: Animate transform rather than width (#​19073)
  • nuxt: Don't include side-effects from #components (#​19008)
🩹 Fixes
  • schema: Allow type inference of arrays in runtime config (#​18931)
  • nuxt: Avoid recursive import in nitro renderer (#​18948)
  • nuxt: Expose nuxt/schema subpath for augmentation (#​18922)
  • nitro: Ensure ssr error statusCode is a number (#​19001)
  • nuxt: Prevent hyphens forming child routes & warn if dupes are detected (#​18944)
  • schema: Transpile nuxt/app by default (#​19009)
  • vite: Exclude nuxt/app from optimised deps (9e789c76c)
  • vite: Respect isCustomElement config for jsx transform (#​19053)
  • nuxt: Use parser to treeshake client-only declarations (#​18951)
  • cli: Pass through exit code from test errors (#​18959)
  • nuxt: Show client error if no page matches after validate fails (#​18978)
  • cli: Read devServer options from nuxt config (#​19055)
  • nuxt: Validate no // in path when constructing payload url (#​19085)
  • nuxt: Restore previous check on payload url (e9ff34ace)
  • nuxt: Test generated pathname (af55b9882)
  • nuxt: Respect redirects which differ only by trailing slash (#​18593)
  • nuxt: Pass nuxt + workspace paths when importing builder (#​19099)
💅 Refactors
  • nuxt: Combine imports from same relative path (ee2f568fc)
📖 Documentation
📦 Build
🏡 Chore
✅ Tests
  • Skip vnode warning on windows dev mode (71bcd9550)
🤖 CI
  • Run webpack/vite and dev/prod as matrices (#​18905)
❤️ Contributors

v3.2.1

Compare Source

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.54.0

Compare Source

Features
  • eslint-plugin: [promise-function-async] check for promises in implicit return types (#​6330) (de1e5ce), closes #​6329

v5.53.0

Compare Source

Features
  • eslint-plugin: [consistent-generic-constructors] handle default parameters (#​6484) (e8cebce)
  • eslint-plugin: [no-mixed-enums] add rule (#​6102) (16144d1)

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)

v5.51.0

Compare Source

Bug Fixes
Features
  • eslint-plugin: [naming-convention] improve performance by removing unnecessary selectors (#​6376) (3647a1c)
  • eslint-plugin: [no-floating-promises] error on logical expression (#​6356) (f330e06)
  • eslint-plugin: [no-import-type-side-effects] add rule to warn against runtime side effects with verbatimModuleSyntax (#​6394) (b14d3be)
  • eslint-plugin: [strict-boolean-expressions] add allow nullable enum to strict boolean expressions (#​6096) (d4747cd)
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.54.0

Compare Source

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

v5.53.0

Compare Source

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

v5.52.0

Compare Source

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

v5.51.0

Compare Source

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

eslint/eslint

v8.35.0

Compare Source

Features

  • 8e34a04 feat: add afterHashbangComment option to lines-around-comment rule (#​16920) (SUZUKI Sosuke)
  • c8c0c71 feat: Move all and recommended configs into package. (#​16844) (Nicholas C. Zakas)
  • 71f6f0d feat: report more cases with ?? in no-constant-binary-expression (#​16826) (Daiki Nishikawa)

Bug Fixes

Documentation

Chores

pnpm/pnpm

v7.28.0

Compare Source

Minor Changes

  • Add --report-summary for pnpm exec and pnpm run #​6008.
  • Show path info for pnpm why --json or --long #​6103.
  • Extend the pnpm.peerDependencyRules.allowedVersions package.json option to support the parent>child selector syntax. This syntax allows for extending specific peerDependencies #​6108.

Patch Changes

  • Update the lockfile if a workspace has a new project with no dependencies.
  • Fix a case of installs not being deterministic and causing lockfile changes between repeat installs. When a dependency only declares peerDependenciesMeta and not peerDependencies, dependencies, or optionalDependencies, the dependency's peers were not considered deterministically before.
  • patch-commit should auto apply patches in workspaces #​6048
  • Automatically fix conflicts in v6 lockfile.
  • pnpm config set should write to the global config file by default #​5877.

Our Gold Sponsors

Our Silver Sponsors

v7.27.1

Compare Source

Patch Changes

  • Add store path description to the pnpm cli help.
  • Print a hint that suggests to run pnpm store prune, when a tarball integrity error happens.
  • Don't retry installation if the integrity checksum of a package failed and no lockfile was present.
  • Fail with a meaningful error message when cannot parse a proxy URL.
  • The strict-ssl, ca, key, and cert settings should work with HTTPS proxy servers #​4689.

Our Gold Sponsors

Our Silver Sponsors

v7.27.0

Compare Source

Minor Changes

  • A new resolution-mode added: lowest-direct. With this resolution mode direct dependencies will be resolved to their lowest versions. So if there is foo@^1.1.0 in the dependencies, then 1.1.0 will be installed, even if the latest version of foo is 1.2.0.
  • Support script selector with RegExp such as pnpm run /build:.*/ and execute the matched scripts with the RegExp #​5871.

Patch Changes

  • Fix version number replacing for namespaced workspace packages. workspace:@&#8203;foo/bar@* should be replaced with npm:@&#8203;foo/bar@<version> on publish #​6052.

  • When resolving dependencies, prefer versions that are already used in the root of the project. This is important to minimize the number of packages that will be nested during hoisting #​6054.

  • Deduplicate direct dependencies.

    Let's say there are two projects in the workspace that dependend on foo. One project has foo@1.0.0 in the dependencies while another one has foo@^1.0.0 in the dependencies. In this case, foo@1.0.0 should be installed to both projects as satisfies the version specs of both projects.

  • Use Map rather than Object in createPackageExtender to prevent read the prototype property to native function

Our Gold Sponsors

Our Silver Sponsors

prettier/prettier

v2.8.4

Compare Source

diff

Fix leading comments in mapped types with readonly (#​13427 by @​thorn0, @​sosukesuzuki)
// Input
type Type = {
  // comment
  readonly [key in Foo];
};

// Prettier 2.8.3
type Type = {
  readonly // comment
  [key in Foo];
};

// Prettier 2.8.4
type Type = {
  // comment
  readonly [key in Foo];
};
Group params in opening block statements (#​14067 by @​jamescdavis)

This is a follow-up to #​13930 to establish wrapping consistency between opening block statements and else blocks by
grouping params in opening blocks. This causes params to break to a new line together and not be split across lines
unless the length of params exceeds the print width. This also updates the else block wrapping to behave exactly the
same as opening blocks.

{{! Input }}
{{#block param param param param param param param param param param as |blockParam|}}
  Hello
{{else block param param param param param param param param param param as |blockParam|}}
  There
{{/block}}

{{! Prettier 2.8.3 }}
{{#block
  param
  param
  param
  param
  param
  param
  param
  param
  param
  param
  as |blockParam|
}}
  Hello
{{else block param
param
param
param
param
param
param
param
param
param}}
  There
{{/block}}

{{! Prettier 2.8.4 }}
{{#block
  param param param param param param param param param param
  as |blockParam|
}}
  Hello
{{else block
  param param param param param param param param param param
  as |blockParam|
}}
  There
{{/block}}
Ignore files in .sl/ (#​14206 by @​bolinfest)

In Sapling SCM, .sl/ is the folder where it stores its state, analogous to .git/ in Git. It should be ignored in Prettier like the other SCM folders.

Recognize @satisfies in Closure-style type casts (#​14262 by @​fisker)
// Input
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});

// Prettier 2.8.3
const a = /** @&#8203;satisfies {Record<string, string>} */ { hello: 1337 };
const b = /** @&#8203;type {Record<string, string>} */ ({ hello: 1337 });

// Prettier 2.8.4
const a = /** @&#8203;satisfies {Record<string, string>} */ ({hello: 1337});
const b = /** @&#8203;type {Record<string, string>} */ ({hello: 1337});
Fix parens in inferred function return types with extends (#​14279 by @​fisker)
// Input
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;

// Prettier 2.8.3 (First format)
type Foo<T> = T extends (a) => a is infer R extends string ? R : never;

// Prettier 2.8.3 (Second format)
SyntaxError: '?' expected. 

// Prettier 2.8.4
type Foo<T> = T extends ((a) => a is infer R extends string) ? R : never;
vitest-dev/vitest

v0.29.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.29.0

Compare Source

This release makes some significant changes to how tests are running. If you were using --no-threads before, you might consider enabling --single-thread instead (because your tests are now running in child_process instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (like process.chdir(), you can now use this option.

One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with --no-isolate, --no-threads or --single-thread - you might need to update your setup files if you were relying on a global variable before.

If you had performance issues on large code bases before, try the new deps.experimentalOptimizer option instead of disabling threads. Feedback is welcome!

One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 force-pushed the renovate/all-minor-patch branch 5 times, most recently from 957832b to 4e186eb Compare February 18, 2023 03:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from ed58987 to 10ff3fe Compare February 26, 2023 13:49
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b08c16f to 0cfd619 Compare February 28, 2023 13:23
@tobiasdiez tobiasdiez merged commit aaa47ae into main Mar 2, 2023
@tobiasdiez tobiasdiez deleted the renovate/all-minor-patch branch March 2, 2023 13:01
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

1 participant