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

chore(deps): update moderndash repo dependencies #185

Open
wants to merge 1 commit into
base: main
Choose a base branch
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
@changesets/cli (source) 2.27.10 -> 2.27.11 age adoption passing confidence
@vitest/coverage-v8 (source) 2.1.5 -> 3.0.3 age adoption passing confidence
@vitest/ui (source) 2.1.5 -> 3.0.3 age adoption passing confidence
typedoc (source) 0.26.11 -> 0.27.6 age adoption passing confidence
typescript (source) 5.6.3 -> 5.7.3 age adoption passing confidence
vite (source) 5.4.11 -> 6.0.11 age adoption passing confidence
vite-tsconfig-paths 5.1.3 -> 5.1.4 age adoption passing confidence
vitest (source) 2.1.5 -> 3.0.3 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.27.11

Compare Source

Patch Changes
vitest-dev/vitest (@​vitest/coverage-v8)

v3.0.3

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v3.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.0.0

Compare Source

Vitest 3 is here! There are a few breaking changes, but we expect the migration to be smooth. This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v2.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v2.1.6

Compare Source

🚀 Features

  • Support VIte 6
    View changes on GitHub
TypeStrong/TypeDoc (typedoc)

v0.27.6

Compare Source

Features
  • Added ignoredHighlightLanguages option to specify languages which will be
    allowed in code blocks but not highlighted, #​2819.
Bug Fixes
  • @include and @includeCode now work in the readme file, #​2814.
  • TypeDoc will now avoid making references to references, #​2811.
  • Fixed output specific option specification, #​2818.
  • Improved type reference conversion to avoid including defaulted type arguments, #​2820.
  • Fixed parsing of declaration references which include a module and a local reference, #​2810.
  • Improved link resolution logic to prioritize type alias properties with the
    same symbol over type literal properties within function parameters.

v0.27.5

Compare Source

Bug Fixes
  • Possibly Breaking: TypeDoc will no longer render anchors within the page for
    deeply nested properties. This only affects links to properties of
    properties of types, which did not have a clickable link exposed so are
    unlikely to have been linked to. Furthermore, these links were not always
    created by TypeDoc, only being created if all parent properties contained
    comments, #​2808.
  • TypeDoc will now warn if a property which does not have a URL within the
    rendered document and the parent property/page will be linked to instead,
    #​2808. These warnings can be disabled with the validation.rewrittenLink
    option.
  • Fix restoration of groups/categories including documents, #​2801.
  • Fixed missed relative paths within markdown link references in documents.
  • Improved handling of incomplete inline code blocks within markdown.
  • Direct https:// links under the hostedBaseUrl option's URL will no
    longer be treated as external, #​2809.
Thanks!

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](https://redirect.github.com/TypeStrong/TypeDoc/iss

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" (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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Nov 25, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
(node:1040) ExperimentalWarning: CommonJS module /opt/containerbase/tools/npm/11.0.0/23.3.0/node_modules/npm/node_modules/debug/src/node.js is loading ES Module /opt/containerbase/tools/npm/11.0.0/23.3.0/node_modules/npm/node_modules/supports-color/index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sveltejs/[email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"6.0.11" from the root project
npm error   vite@"^5.0.0 || ^6.0.0" from [email protected]
npm error   node_modules/vitest
npm error     dev vitest@"3.0.3" from the root project
npm error     peer vitest@"3.0.3" from @vitest/[email protected]
npm error     node_modules/@vitest/coverage-v8
npm error       dev @vitest/coverage-v8@"3.0.3" from the root project
npm error     1 more (@vitest/ui)
npm error   1 more (vite-tsconfig-paths)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^5.0.3" from @sveltejs/[email protected]
npm error node_modules/@sveltejs/kit
npm error   peer @sveltejs/kit@"^2.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/adapter-static
npm error     dev @sveltejs/adapter-static@"3.0.1" from documentation-website@undefined
npm error     website
npm error       documentation-website@undefined
npm error       node_modules/documentation-website
npm error   dev @sveltejs/kit@"2.5.9" from documentation-website@undefined
npm error   website
npm error     documentation-website@undefined
npm error     node_modules/documentation-website
npm error       workspace website from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^5.0.3" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     peer @sveltejs/kit@"^2.0.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-static
npm error       dev @sveltejs/adapter-static@"3.0.1" from documentation-website@undefined
npm error       website
npm error         documentation-website@undefined
npm error         node_modules/documentation-website
npm error     dev @sveltejs/kit@"2.5.9" from documentation-website@undefined
npm error     website
npm error       documentation-website@undefined
npm error       node_modules/documentation-website
npm error         workspace website from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-21T18_49_12_526Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-21T18_49_12_526Z-debug-0.log

Copy link

changeset-bot bot commented Nov 25, 2024

⚠️ No Changeset found

Latest commit: e675846

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

Copy link

netlify bot commented Nov 25, 2024

Deploy Preview for moderndash failed.

Name Link
🔨 Latest commit e675846
🔍 Latest deploy log https://app.netlify.com/sites/moderndash/deploys/678fec372fd6780007d028d3

@renovate renovate bot force-pushed the renovate/moderndash-repo branch from 3c10de3 to 64ed4e2 Compare November 26, 2024 15:21
@renovate renovate bot changed the title chore(deps): update dependency typescript to v5.7.2 chore(deps): update moderndash repo dependencies Nov 26, 2024
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 7 times, most recently from de778b3 to cde8823 Compare December 2, 2024 16:00
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 4 times, most recently from 898491d to 1559294 Compare December 9, 2024 03:07
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 4 times, most recently from 44a6803 to f7e97ce Compare December 20, 2024 13:27
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 2 times, most recently from bbbaee2 to 02885e6 Compare December 26, 2024 05:20
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 2 times, most recently from 3aa412d to 2e56f59 Compare January 8, 2025 22:58
@renovate renovate bot force-pushed the renovate/moderndash-repo branch 5 times, most recently from 3404749 to 36359bc Compare January 20, 2025 20:58
@renovate renovate bot force-pushed the renovate/moderndash-repo branch from 36359bc to 3e19090 Compare January 21, 2025 13:46
@renovate renovate bot force-pushed the renovate/moderndash-repo branch from 3e19090 to e675846 Compare January 21, 2025 18:49
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