Skip to content

Update all dependencies #71

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.

Sign up for GitHub

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

Jump to bottom
Merged
renovate merged 1 commit into from
May 9, 2025
Merged

Update all dependencies #71

renovate merged 1 commit into from
May 9, 2025

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 12, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@astrojs/react (source) 4.2.3 -> 4.2.7 age adoption passing confidence
@astrojs/starlight (source) 0.33.0 -> 0.34.2 age adoption passing confidence
@astrojs/starlight-tailwind (source) 3.0.1 -> 4.0.1 age adoption passing confidence
@changesets/cli (source) 2.28.1 -> 2.29.3 age adoption passing confidence
@types/node (source) 22.14.0 -> 22.15.14 age adoption passing confidence
@types/react (source) 19.1.0 -> 19.1.3 age adoption passing confidence
@types/react-dom (source) 19.1.2 -> 19.1.3 age adoption passing confidence
astro (source) 5.6.1 -> 5.7.11 age adoption passing confidence
lint-staged 15.5.0 -> 15.5.2 age adoption passing confidence
tailwindcss (source) 4.1.3 -> 4.1.5 age adoption passing confidence
turbo (source) 2.5.0 -> 2.5.3 age adoption passing confidence
vitest (source) 3.1.1 -> 3.1.3 age adoption passing confidence

Release Notes

withastro/astro (@​astrojs/react)

v4.2.7

Compare Source

Patch Changes

v4.2.6

Compare Source

Patch Changes

v4.2.5

Compare Source

Patch Changes

v4.2.4

Compare Source

Patch Changes
withastro/starlight (@​astrojs/starlight)

v0.34.2

Compare Source

Patch Changes

v0.34.1

Compare Source

Patch Changes

  • #​3140 f6eb1d5 Thanks @​HiDeoo! - Fixes a text selection issue for heading with a clickable anchor link when using double or triple click to select text.

  • #​3148 dc8b6d5 Thanks @​HiDeoo! - Fixes a regression of the Starlight icon color when using the credits configuration option.

v0.34.0

Compare Source

Minor Changes

  • #​2322 f14eb0c Thanks @​HiDeoo! - Groups all of Starlight's CSS declarations into a single starlight cascade layer.

    This change allows for easier customization of Starlight's CSS as any custom unlayered CSS will override the default styles. If you are using cascade layers in your custom CSS, you can use the @layer CSS at-rule to define the order of precedence for different layers including the ones used by Starlight.

    We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

  • #​3122 3a087d8 Thanks @​delucis! - Removes default attrs and content values from head entries parsed using Starlight’s schema.

    Previously when adding head metadata via frontmatter or user config, Starlight would automatically add values for attrs and content if not provided. Now, these properties are left undefined.

    This makes it simpler to add tags in route middleware for example as you no longer need to provide empty values for attrs and content:

    head.push({
  tag: 'style',
  content: 'div { color: red }'
- attrs: {},
});
head.push({
  tag: 'link',
- content: ''
  attrs: { rel: 'me', href: 'https://example.com' },
});

    This is mostly an internal API but if you are overriding Starlight’s Head component or processing head entries in some way, you may wish to double check your handling of Astro.locals.starlightRoute.head is compatible with attrs and content potentially being undefined.

  • #​3033 8c19678 Thanks @​delucis! - Adds support for generating clickable anchor links for headings.

    By default, Starlight now renders an anchor link beside headings in Markdown and MDX content. A new <AnchorHeading> component is available to achieve the same thing in custom pages built using <StarlightPage>.

    If you want to disable this new Markdown processing set the markdown.headingLinks option in your Starlight config to false:

    starlight({
  title: 'My docs',
  markdown: {
    headingLinks: false,
  },
}),

    ⚠️ BREAKING CHANGE: The minimum supported version of Astro is now v5.5.0.

    Please update Starlight and Astro together:

    npx @&#8203;astrojs/upgrade

  • #​2322 f14eb0c Thanks @​HiDeoo! - Removes Shiki css-variables theme fallback.

    ⚠️ BREAKING CHANGE:

    Previously, Starlight used to automatically provide a fallback theme for Shiki, the default syntax highlighter built into Astro if the configured Shiki theme was not github-dark.

    This fallback was only relevant when the default Starlight code block renderer, Expressive Code, was disabled and Shiki was used. Starlight no longer provides this fallback.

    If you were relying on this behavior, you now manually need to update your Astro configuration to use the Shiki css-variables theme to match the previous behavior.

    import { defineConfig } from 'astro/config';

export default defineConfig({
+ markdown: {
+   shikiConfig: {
+     theme: 'css-variables',
+   },
+ },
});

    Additionally, you can use custom CSS to control the appearance of the code blocks. Here are the previously used CSS variables for the fallback theme:

    :root {
  --astro-code-foreground: var(--sl-color-white);
  --astro-code-background: var(--sl-color-gray-6);
  --astro-code-token-constant: var(--sl-color-blue-high);
  --astro-code-token-string: var(--sl-color-green-high);
  --astro-code-token-comment: var(--sl-color-gray-2);
  --astro-code-token-keyword: var(--sl-color-purple-high);
  --astro-code-token-parameter: var(--sl-color-red-high);
  --astro-code-token-function: var(--sl-color-red-high);
  --astro-code-token-string-expression: var(--sl-color-green-high);
  --astro-code-token-punctuation: var(--sl-color-gray-2);
  --astro-code-token-link: var(--sl-color-blue-high);
}
Patch Changes
  • #​3118 77a1104 Thanks @​delucis! - Fixes passing imported SVGs to the frontmatter prop of the <StarlightPage> component in Astro ≥5.7.0

v0.33.2

Compare Source

Patch Changes

v0.33.1

Compare Source

Patch Changes

  • #​3088 1885049 Thanks @​HiDeoo! - Fixes a regression in Starlight version 0.33.0 that caused the description and links to language alternates for multilingual websites to be missing from the <head> of the page.

  • #​3065 463adf5 Thanks @​HiDeoo! - Updates the social configuration option TSDoc example to match the shape of the expected value.

withastro/starlight (@​astrojs/starlight-tailwind)

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes

  • #​2322 f14eb0c Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: The minimum supported version of Starlight is now 0.34.0

    Please use the @astrojs/upgrade command to upgrade your project:

    npx @&#8203;astrojs/upgrade

  • #​2322 f14eb0c Thanks @​HiDeoo! - Adds support for Tailwind v4, drops support for Tailwind v3.

    ⚠️ BREAKING CHANGE: Tailwind v3 is no longer supported. Tailwind v4 support in Astro is now provided using a Vite plugin and the Astro Tailwind integration is no longer required.

    1. Remove the Astro Tailwind integration. The Astro Tailwind integration is no longer required with Tailwind v4.

       // astro.config.mjs
 import { defineConfig } from "astro/config";
 import starlight from "@&#8203;astrojs/starlight";
-import tailwind from "@&#8203;astrojs/tailwind";

 export default defineConfig({
   integrations: [
     starlight({
       title: "Docs with Tailwind",
       customCss: ["./src/tailwind.css"],
     }),
-    tailwind({ applyBaseStyles: false }),
   ],
 });

    2. Install Tailwind v4. Install the latest version of the tailwindcss and @tailwindcss/vite packages.

      Use the astro add tailwind command to install and configure both packages:

      npx astro add tailwind

    3. Update Tailwind base styles. Tailwind CSS base styles needs to be updated for Tailwind v4 and also to use Starlight Tailwind CSS.

      /* src/tailwind.css */
-@&#8203;tailwind base;
-@&#8203;tailwind components;
-@&#8203;tailwind utilities;
+@&#8203;layer base, starlight, theme, components, utilities;
+
+@&#8203;import '@&#8203;astrojs/starlight-tailwind';
+@&#8203;import 'tailwindcss/theme.css' layer(theme);
+@&#8203;import 'tailwindcss/utilities.css' layer(utilities);
+
+@&#8203;theme {
+	/*
+	Configure your Tailwind theme that will be used by Starlight.
+	https://starlight.astro.build/guides/css-and-tailwind/#styling-starlight-with-tailwind
+	*/
+}
+
+/*
+Add additional Tailwind styles to this file:
+https://tailwindcss.com/docs/adding-custom-styles#using-custom-css
+*/

    4. Update Tailwind customizations. If you previously customized your Tailwind theme configuration in the tailwind.config.mjs file, such customizations are now defined through CSS using the @theme block in your Tailwind base styles.

      1. Locate existing customizations in your tailwind.config.mjs file. The following example defines customizations for the accent colors, gray scale, and font families used by Starlight:

        // tailwind.config.mjs
import starlightPlugin from '@&#8203;astrojs/starlight-tailwind';
import colors from 'tailwindcss/colors';

/** @&#8203;type {import('tailwindcss').Config} */
export default {
  content: ['./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}'],
  theme: {
    extend: {
      colors: {
        // Custom accent colors.
        accent: colors.fuchsia,
        // Custom gray scale.
        gray: colors.slate,
      },
      fontFamily: {
        // Custom text font.
        sans: ['"Atkinson Hyperlegible"'],
        // Custom code font.
        mono: ['"IBM Plex Mono"'],
      },
    },
  },
  plugins: [starlightPlugin()],
};

      2. The above customizations can be migrated to the new @theme block in the file containing your Tailwind base styles as follows:

        /* src/tailwind.css */
@&#8203;layer base, starlight, theme, components, utilities;

@&#8203;import '@&#8203;astrojs/starlight-tailwind';
@&#8203;import 'tailwindcss/theme.css' layer(theme);
@&#8203;import 'tailwindcss/utilities.css' layer(utilities);

@&#8203;theme {
  /* Custom accent colors. */
  --color-accent-50: var(--color-fuchsia-50);
  --color-accent-100: var(--color-fuchsia-100);
  --color-accent-200: var(--color-fuchsia-200);
  --color-accent-300: var(--color-fuchsia-300);
  --color-accent-400: var(--color-fuchsia-400);
  --color-accent-500: var(--color-fuchsia-500);
  --color-accent-600: var(--color-fuchsia-600);
  --color-accent-700: var(--color-fuchsia-700);
  --color-accent-800: var(--color-fuchsia-800);
  --color-accent-900: var(--color-fuchsia-900);
  --color-accent-950: var(--color-fuchsia-950);
  /* Custom gray scale. */
  --color-gray-50: var(--color-slate-50);
  --color-gray-100: var(--color-slate-100);
  --color-gray-200: var(--color-slate-200);
  --color-gray-300: var(--color-slate-300);
  --color-gray-400: var(--color-slate-400);
  --color-gray-500: var(--color-slate-500);
  --color-gray-600: var(--color-slate-600);
  --color-gray-700: var(--color-slate-700);
  --color-gray-800: var(--color-slate-800);
  --color-gray-900: var(--color-slate-900);
  --color-gray-950: var(--color-slate-950);
  /* Custom text font. */
  --font-sans: 'Atkinson Hyperlegible';
  /* Custom code font. */
  --font-mono: 'IBM Plex Mono';
}

    We recommend checking your site’s appearance when upgrading to make sure there are no style regressions caused by this change.

    For full details about upgrading from Tailwind v3 to v4, see the official upgrade guide.

changesets/changesets (@​changesets/cli)

v2.29.3

Compare Source

Patch Changes

v2.29.2

Compare Source

Patch Changes

v2.29.1

Compare Source

Patch Changes

v2.29.0

Compare Source

Minor Changes
withastro/astro (astro)

v5.7.11

Compare Source

Patch Changes

v5.7.10

Compare Source

Patch Changes

v5.7.9

Compare Source

Patch Changes

v5.7.8

Compare Source

Patch Changes

v5.7.7

Compare Source

Patch Changes

v5.7.6

Compare Source

Patch Changes

  • #​13703 659904b Thanks @​ascorbic! - Fixes a bug where empty fallbacks could not be provided when using the experimental fonts API

  • #​13680 18e1b97 Thanks @​florian-lefebvre! - Improves the UnsupportedExternalRedirect error message to include more details such as the concerned destination

  • #​13703 659904b Thanks @​ascorbic! - Simplifies styles for experimental responsive images

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️

    The generated styles for image layouts are now simpler and easier to override. Previously the responsive image component used CSS to set the size and aspect ratio of the images, but this is no longer needed. Now the styles just include object-fit and object-position for all images, and sets max-width: 100% for constrained images and width: 100% for full-width images.

    This is an implementation change only, and most users will see no change. However, it may affect any custom styles you have added to your responsive images. Please check your rendered images to determine whether any change to your CSS is needed.

    The styles now use the :where() pseudo-class, which has a specificity of 0, meaning that it is easy to override with your own styles. You can now be sure that your own classes will always override the applied styles, as will global styles on img.

    An exception is Tailwind 4, which uses cascade layers, meaning the rules are always lower specificity. Astro supports browsers that do not support cascade layers, so we cannot use this. If you need to override the styles using Tailwind 4, you must use !important classes. Do check if this is needed though: there may be a layout that is more appropriate for your use case.

  • #​13703 659904b Thanks @​ascorbic! - Adds warnings about using local font files in the publicDir when the experimental fonts API is enabled.

  • #​13703 659904b Thanks @​ascorbic! - Renames experimental responsive image layout option from "responsive" to "constrained"

    ⚠️ BREAKING CHANGE FOR EXPERIMENTAL RESPONSIVE IMAGES ONLY ⚠️

    The layout option called "responsive" is renamed to "constrained" to better reflect its behavior.

    The previous name was causing confusion, because it is also the name of the feature. The responsive layout option is specifically for images that are displayed at the requested size, unless they do not fit the width of their container, at which point they would be scaled down to fit. They do not get scaled beyond the intrinsic size of the source image, or the width prop if provided.

    It became clear from user feedback that many people (understandably) thought that they needed to set layout to responsive if they wanted to use responsive images. They then struggled with overriding styles to make the image scale up for full-width hero images, for example, when they should have been using full-width layout. Renaming the layout to constrained should make it clearer that this layout is for when you want to constrain the maximum size of the image, but allow it to scale-down.

Upgrading

If you set a default image.experimentalLayout in your astro.config.mjs, or set it on a per-image basis using the layout prop, you will need to change all occurences to constrained:

// astro.config.mjs
export default {
  image: {
-    experimentalLayout: 'responsive',
+    experimentalLayout: 'constrained',
  },
}

v5.7.5

Compare Source

Patch Changes

v5.7.4

Compare Source

Patch Changes

v5.7.3

Compare Source

Patch Changes

v5.7.2

Compare Source

Patch Changes

v5.7.1

Compare Source

Patch Changes

v5.7.0

Compare Source

Minor Changes

  • #​13527 2fd6a6b Thanks @​ascorbic! - The experimental session API introduced in Astro 5.1 is now stable and ready for production use.

    Sessions are used to store user state between requests for on-demand rendered pages. You can use them to store user data, such as authentication tokens, shopping cart contents, or any other data that needs to persist across requests:

v5.6.2

Compare Source

Patch Changes

  • #​13606 793ecd9 Thanks @​natemoo-re! - Fixes a regression that allowed prerendered code to leak into the server bundle.

  • #​13576 1c60ec3 Thanks @​ascorbic! - Reduces duplicate code in server islands scripts by extracting shared logic into a helper function.

  • #​13588 57e59be Thanks @​natemoo-re! - Fixes a memory leak when using SVG assets.

  • #​13589 5a0563d Thanks @​ematipico! - Deprecates the asset utility function emitESMImage() and adds a new emitImageMetadata() to be used instead

    The function
    emitESMImage() is now deprecated. It will continue to function, but it is no longer recommended nor supported. This function will be completely removed in a next major release of Astro.

    Please replace it with the new functionemitImageMetadata() as soon as you are able to do so:

    - import { emitESMImage } from "astro/assets/utils";
+ import { emitImageMetadata } from "astro/assets/utils";

    The new function returns the same signature as the previous one. However, the new function removes two deprecated arguments that were not meant to be exposed for public use: _watchMode and experimentalSvgEnabled. Since it was possible to access these with the old function, you may need to verify that your code still works as intended with emitImageMetadata().

  • [#&Update dependency @biomejs/biome to v2.0.4 #82

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC).

🚦 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.

@vercel
Copy link

vercel bot commented Apr 12, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
npm-module-template ❌ Failed (Inspect) May 9, 2025 10:20pm

@renovate renovate bot enabled auto-merge (squash) April 12, 2025 13:41
@changeset-bot
Copy link

changeset-bot bot commented Apr 12, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: a1e4818

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 changed the title Update all dependencies Update dependency @astrojs/starlight to v0.33.1 Apr 14, 2025
@renovate renovate bot changed the title Update dependency @astrojs/starlight to v0.33.1 Update all dependencies Apr 14, 2025
@renovate renovate bot force-pushed the renovate/all branch from 01423cc to efac1d8 Compare May 8, 2025 12:48
auto-merge was automatically disabled May 8, 2025 12:48

Head branch was modified

@renovate renovate bot enabled auto-merge (squash) May 8, 2025 19:33
@renovate renovate bot force-pushed the renovate/all branch from 06a1122 to b7c6b54 Compare May 8, 2025 19:33
@renovate renovate bot force-pushed the renovate/all branch from 9cd6f8a to d1c44ba Compare May 8, 2025 23:12
@renovate renovate bot force-pushed the renovate/all branch from 9de5e37 to 1e91659 Compare May 9, 2025 02:51
@renovate renovate bot force-pushed the renovate/all branch from c19f5af to 392add4 Compare May 9, 2025 07:05
@renovate renovate bot force-pushed the renovate/all branch from 553bb98 to f72b2f0 Compare May 9, 2025 11:19
@renovate renovate bot force-pushed the renovate/all branch from 6c2341d to d4f3fd0 Compare May 9, 2025 20:08
@renovate renovate bot force-pushed the renovate/all branch from 5c6d71b to a1e4818 Compare May 9, 2025 22:20
@renovate renovate bot merged commit 63b2ed1 into main May 9, 2025
4 of 5 checks passed
@renovate renovate bot deleted the renovate/all branch May 9, 2025 22:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant