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

fix(deps): update all dependencies #857

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update all dependencies #857

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@changesets/cli (source) 2.27.9 -> 2.27.10 age adoption passing confidence dependencies patch
@manypkg/cli (source) 0.22.0 -> 0.23.0 age adoption passing confidence dependencies minor
@opentelemetry/auto-instrumentations-node (source) ^0.52.0 -> ^0.54.0 age adoption passing confidence dependencies minor
@opentelemetry/exporter-metrics-otlp-http (source) ^0.54.0 -> ^0.56.0 age adoption passing confidence dependencies minor
@opentelemetry/sdk-node (source) ^0.54.0 -> ^0.56.0 age adoption passing confidence dependencies minor
dotenv 16.4.5 -> 16.4.7 age adoption passing confidence devDependencies patch
node (source) 20.18.0 -> 20.18.1 age adoption passing confidence patch
prettier (source) 3.3.3 -> 3.4.2 age adoption passing confidence dependencies minor
typedoc (source) ^0.26.0 -> ^0.27.0 age adoption passing confidence dependencies minor
typescript (source) 5.6.3 -> 5.7.2 age adoption passing confidence dependencies minor

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.10

Compare Source

Thinkmill/manypkg (@​manypkg/cli)

v0.23.0

Compare Source

Minor Changes
  • #​236 1a5ea55 Thanks @​VanTanev! - Change the ROOT_HAS_DEV_DEPENDENCIES rule to ROOT_HAS_PROD_DEPENDENCIES. Monorepo root should use devDependencies instead of dependencies for better support of production-only installs, useful in eg Docker builds.
open-telemetry/opentelemetry-js-contrib (@​opentelemetry/auto-instrumentations-node)

v0.54.0

Compare Source

v0.53.0

Compare Source

open-telemetry/opentelemetry-js (@​opentelemetry/exporter-metrics-otlp-http)

v0.56.0

Compare Source

v0.55.0

Compare Source

motdotla/dotenv (dotenv)

v16.4.7

Compare Source

Changed
  • Ignore .tap folder when publishing. (oops, sorry about that everyone. - @​motdotla) #​848

v16.4.6

Compare Source

Changed
  • Clean up stale dev dependencies #​847
  • Various README updates clarifying usage and alternative solutions using dotenvx
nodejs/node (node)

v20.18.1: 2024-11-20, Version 20.18.1 'Iron' (LTS), @​marco-ippolito

Compare Source

Notable Changes
Commits
prettier/prettier (prettier)

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)
// Input
class A {
  @&#8203;decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @&#8203;decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @&#8203;decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}
Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.1

Compare Source

diff

Remove unnecessary parentheses around assignment in v-on (#​16887 by @​fisker)
<!-- Input -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

<!-- Prettier 3.4.0 -->
<template>
  <button @&#8203;click="(foo += 2)">Click</button>
</template>

<!-- Prettier 3.4.1 -->
<template>
  <button @&#8203;click="foo += 2">Click</button>
</template>

v3.4.0

Compare Source

diff

🔗 Release Notes

TypeStrong/TypeDoc (typedoc)

v0.27.4

Compare Source

Features
  • API: Introduced new Converter.EVENT_CREATE_PROJECT event which fires when a project is created by the converter, #​2800.
Bug Fixes
  • Switch from gzip to deflate for compressing assets to make output consistent across different operating systems, #​2796.
  • @include and @includeCode now work for comments on the entry point for projects with a single entry point, #​2800.
  • Cascaded modifier tags will no longer be copied into type literals, #​2802.
  • @summary now works to describe functions within modules, #​2803.
  • Corrected navigation showing module link as current when not on module page, #​2805.

v0.27.3

Compare Source

Features
  • Added support for PNG favicons, #​2790.
  • Improved support for hosting TypeDoc with strict Content Security Policy rules, #​2794.
Bug Fixes
  • Add special handling for import types with type errors discarded with ts-expect-error, #​2792.
  • Fixed low contrast in default colors for properties/accessors in light mode, #​2795.
  • The highlightLanguages option now permits Shiki aliases to be specified rather than just the language ID, #​2798.
Thanks!

v0.27.2

Compare Source

Bug Fixes
  • Fix crash with TypeScript 5.5.x, #​2789.

v0.27.1

Compare Source

Bug Fixes
  • Include classes which inherit from another package in class hierarchy in packages mode, #​2467.
  • Fixed handling of @categoryDescription and @groupDescription on module pages, #​2787.
  • Fixed automatic discovery of entry points in packages mode.
  • Reverted accidental style change for hierarchy page introduced in 0.27.0
  • The hierarchy Expand/Collapse link will now only appear if the hierarchies are different.

v0.27.0

Compare Source

Breaking Changes
  • Convert to ESM to enable easier use of ESM-only dependencies.
  • Drop support for TypeScript <5.0, no longer supported by DefinitelyTyped
  • Relaxed requirements for file names and generated url fragments. This may
    result in a different file name structure, #​2714.
  • Anchors to document headings and reflections within a HTML generated pages
    have changed. They can be partially restored to the previous format by
    setting --sluggerConfiguration.lowercase false. This change was made to
    more closely match the default behavior of GitHub's markdown rendering and
    VSCode's autocomplete when creating a relative link to an external markdown
    file.
  • Removed the hideParameterTypesInTitle option, this was originally added as
    a workaround for many signatures overflowing the available horizontal space
    in rendered pages. TypeDoc now has logic to wrap types/signatures smartly,
    so this option is no longer necessary.
  • Changed the default kindSortOrder to put references last.
  • Changed the default sort order to use alphabetical-ignoring-documents
    instead of alphabetical.
  • Changed default of suppressCommentWarningsInDeclarationFiles to true
  • API: Constructor signatures now use the parent class name as their name
    (e.g. X, not new X)
  • API: @group, @category, @groupDescription and @categoryDescription
    will no longer be removed from the reflections they are present on. They are
    skipped during rendering with the notRenderedTags option.
Features
  • Add support for TypeScript 5.7
  • TypeDoc will now discover entry points from package.json exports if they
    are not provided manually, #​1937.
  • Relative links to markdown files may now include #anchor links to
    reference a heading within them.
  • Improved support for @param comments with nested object types, #​2555.
  • Improved support for @param comments which reference a type
    alias/interface. Important properties on the referenced type can now be
    highlighted with @param options.foo, which will result in the additional
    note being included under the documentation for that parameter, #​2147. Note:
    This feature is limited to references. It is not supported on other types of
    types.
  • Added a new outputs option which is an array of outputs. This can be used
    to render the documentation multiple times with different rendering options
    or output types, #​2597.
  • Added support for rendering alerts (or callouts) in markdown.
  • Add support for an @expand tag which can be placed on type aliases and
    interfaces. When a type with @expand is referenced and TypeDoc has a place
    to include additional details about the type, the properties of the type
    will be included in the page where @expand is found. Note that use of this
    tag can significantly increase the size of your generated documentation if
    it is applied to commonly used types as it will result in inlining the
    comments for those types everywhere they are referenced, #​2303.
  • Add support for an @inline tag which can be placed on type aliases and
    interfaces. When a type with @inline is referenced, TypeDoc will resolve
    the referenced type and convert the type as if it was included directly
    within the referencing type. Note that use of this tag can significantly
    increase the size of your generated documentation if it is applied to
    commonly used types as it will result in inlining the comments for those
    types everywhere they are referenced, #​2303.
  • Introduced a new @useDeclaredType tag for type aliases which can sometimes
    improve their documentation, #​2654.
  • Added a new @mergeModuleWith tag which can be used to tell TypeDoc to
    place a module/namespace's children under a different module/namespace and
    remove the real parent, #​2281.
  • Added new @include and @includeCode inline tags to include files within
    comments/documents.
  • Add notRenderedTags option. This option is similar to the excludeTags
    option, but while excludeTags will result in the tag being completely
    removed from the documentation, notRenderedTags only prevents it from
    being included when rendering.
  • Added groupReferencesByType option.
  • Added navigation.excludeReferences option
  • Added useFirstParagraphOfCommentAsSummary option to configure how TypeDoc
    handles comments for module members without the @summary tag.
  • Introduced favicon option to specify a .ico or .svg favicon to reference.
  • Sections within the page and in the "On This Page" navigation are now tied
    together and will expand/collapse together, #​2335.
  • API: Introduced a new app.outputs object for defining new output strategies.
  • API: TypeDoc's CSS is now wrapped in @layer typedoc, #​2782.
Bug Fixes
  • TypeDoc now properly flags readonly index signatures.
  • TypeDoc will now use the first signature's comment for later signatures in
    overloads if present, #​2718.
  • Fixed handling of @enum if the type was declared before the variable, #​2719.
  • Fixed empty top level modules page in packages mode, #​2753.
  • TypeDoc can now link to type alias properties, #​2524.
  • TypeDoc will now document the merged symbol type when considering globals
    declared inside declare global, #​2774
  • TypeDoc now converts declare module "foo" as a module rather than a namespace, #​2778.
  • Import types in type aliases now use module member references if present, #​2779.
  • Fixed an issue where properties were not properly marked optional in some
    cases. This primarily affected destructured parameters.
  • Added yaml to the highlight languages supported by default.
  • TypeDoc now recognizes txt as an alias of text to indicate a code block
    should not be highlighted.
  • Items which are hidden with @ignore or @hidden but still referenced by
    other types will no longer produce warnings about not being exported.
  • If a project only has one module within it, TypeDoc will now consider that
    module when resolving @link tags.
  • The arrows to indicate whether or not a section is open now work when
    JavaScript is disabled.
  • Group/category search boosts are now applied when writing the search index
    rather than when converting. This prevents issues where boosts used by just
    one package were incorrectly reported as unused when running with
    entryPointStrategy set to packages.
Thanks!
microsoft/TypeScript (typescript)

v5.7.2

Compare Source


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner November 25, 2024 00:35
Copy link

changeset-bot bot commented Nov 25, 2024

⚠️ No Changeset found

Latest commit: da04c3e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 239cae0 to ae7756f Compare December 3, 2024 03:55
@renovate renovate bot force-pushed the renovate/all branch 18 times, most recently from 146a785 to cbb456f Compare December 10, 2024 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants