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

Merged
merged 1 commit into from
Dec 14, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 8, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@astrojs/starlight (source) ^0.29.2 -> ^0.30.0 age adoption passing confidence dependencies minor
astro (source) ^5.0.1 -> ^5.0.5 age adoption passing confidence dependencies patch
astro-og-canvas (source) ^0.5.4 -> ^0.5.5 age adoption passing confidence dependencies patch
katex (source) ^0.16.11 -> ^0.16.15 age adoption passing confidence dependencies patch
node (source) 22.11.0 -> 22.12.0 age adoption passing confidence minor
pnpm (source) 9.14.4 -> 9.15.0 age adoption passing confidence packageManager minor
prettier (source) ^3.4.1 -> ^3.4.2 age adoption passing confidence devDependencies patch
starlight-links-validator ^0.13.3 -> ^0.13.4 age adoption passing confidence dependencies patch

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.30.0

Compare Source

Minor Changes
Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v4 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @​astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v5. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Starlight's internal content collections, which organize, validate, and render your content, have been updated to use Astro's new Content Layer API and require configuration changes in your project.

  1. Move the content config file. This file no longer lives within the src/content/config.ts folder and should now exist at src/content.config.ts.

  2. Edit the collection definition(s). To update the docs collection, a loader is now required:

     // src/content.config.ts
     import { defineCollection } from "astro:content";
    +import { docsLoader } from "@​astrojs/starlight/loaders";
     import { docsSchema } from "@​astrojs/starlight/schema";
    
     export const collections = {
    -  docs: defineCollection({ schema: docsSchema() }),
    +  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
     };

    If you are using the i18n collection to provide translations for additional languages you support or override our default labels, you will need to update the collection definition in a similar way and remove the collection type which is no longer available:

     // src/content.config.ts
     import { defineCollection } from "astro:content";
    +import { docsLoader, i18nLoader } from "@​astrojs/starlight/loaders";
     import { docsSchema, i18nSchema } from "@​astrojs/starlight/schema";
    
     export const collections = {
    -  docs: defineCollection({ schema: docsSchema() }),
    +  docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
    -  i18n: defineCollection({ type: 'data', schema: i18nSchema() }),
    +  i18n: defineCollection({ loader: i18nLoader(), schema: i18nSchema() }),
     };
  3. Update other collections. To update any other collections you may have, follow the “Updating existing collections” section in the Astro 5 upgrade guide.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collections flag to upgrade to v5 without updating your collections. This legacy flag exists to provide temporary backwards compatibility, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

Patch Changes

v0.29.3

Compare Source

Patch Changes
withastro/astro (astro)

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes
  • #​12645 8704c54 Thanks @​sarah11918! - Updates some reference links in error messages for new v5 docs.

  • #​12641 48ca399 Thanks @​ascorbic! - Fixes a bug where astro info --copy wasn't working correctly on macOS systems.

  • #​12461 62939ad Thanks @​kyr0! - Removes the misleading log message telling that a custom renderer is not recognized while it clearly is and works.

  • #​12642 ff18b9c Thanks @​ematipico! - Provides more information when logging a warning for accessing Astro.request.headers in prerendered pages

  • #​12634 03958d9 Thanks @​delucis! - Improves error message formatting for user config and content collection frontmatter

  • #​12547 6b6e18d Thanks @​mtwilliams-code! - Fixes a bug where URL search parameters weren't passed when using the i18n fallback feature.

  • #​12449 e6b8017 Thanks @​apatel369! - Fixes an issue where the custom assetFileNames configuration caused assets to be incorrectly moved to the server directory instead of the client directory, resulting in 404 errors when accessed from the client side.

  • #​12518 e216250 Thanks @​ematipico! - Fixes an issue where SSR error pages would return duplicated custom headers.

  • #​12625 74bfad0 Thanks @​ematipico! - Fixes an issue where the experimental.svg had incorrect type, resulting in some errors in the editors.

  • #​12631 dec0305 Thanks @​ascorbic! - Fixes a bug where the class attribute was rendered twice on the image component

  • #​12623 0e4fecb Thanks @​ascorbic! - Correctly handles images in content collections with uppercase file extensions

  • #​12633 8a551c1 Thanks @​bluwy! - Cleans up content layer sync during builds and programmatic sync() calls

  • #​12640 22e405a Thanks @​ascorbic! - Fixes a bug that caused content collections to be returned empty when run in a test environment

  • #​12613 306c9f9 Thanks @​matthewp! - Fix use of cloned requests in middleware with clientAddress

    When using context.clientAddress or Astro.clientAddress Astro looks up the address in a hidden property. Cloning a request can cause this hidden property to be lost.

    The fix is to pass the address as an internal property instead, decoupling it from the request.

v5.0.2

Compare Source

Patch Changes
delucis/astro-og-canvas (astro-og-canvas)

v0.5.5

Compare Source

Patch Changes
  • ceeecc1: Expands peer dependencies to support Astro v5
KaTeX/KaTeX (katex)

v0.16.15

Compare Source

Features
  • italic sans-serif in math mode via \mathsfit command (#​3998) (2218901)

v0.16.14

Compare Source

Features

v0.16.13

Compare Source

Bug Fixes

v0.16.12

Compare Source

Features
nodejs/node (node)

v22.12.0

Compare Source

pnpm/pnpm (pnpm)

v9.15.0

Compare Source

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>;
HiDeoo/starlight-links-validator (starlight-links-validator)

v0.13.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - "on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 added the renovate label Dec 8, 2024
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update node.js to v22.12.0 Dec 8, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 2aadf54 to a23a07d Compare December 8, 2024 21:06
@renovate renovate bot changed the title chore(deps): update node.js to v22.12.0 chore(deps): update all non-major dependencies Dec 8, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from b8c6d54 to 7ea2f90 Compare December 11, 2024 22:12
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7ea2f90 to f568a1e Compare December 13, 2024 23:15
@renovate renovate bot merged commit 49a62b8 into main Dec 14, 2024
2 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch December 14, 2024 01:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants