fix(deps): update site (non-major) #121

renovate · 2024-02-26T17:03:39Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/check (source)	`^0.5.5` -> `^0.7.0`
@astrojs/mdx (source)	`2.1.1` -> `2.3.1`
@astrojs/preact (source)	`3.1.1` -> `3.5.0`
@astrojs/rss (source)	`4.0.5` -> `4.0.7`
@astrojs/sitemap (source)	`3.1.1` -> `3.1.6`
astro (source)	`4.4.4` -> `4.11.3`
typescript (source)	`5.3.3` -> `5.5.2`

Release Notes

withastro/language-tools (@astrojs/check)

`v0.7.0`

Compare Source

Minor Changes

c8af6db: Upgrades the language server to use the latest version of Volar. This changes should have no negative impacts on the experience.

Patch Changes

Updated dependencies [c8af6db]
- @astrojs/language-server @2.10.0

`v0.6.0`

Compare Source

Minor Changes

65d3425: Upgrades the language server to use Volar 2.2. This changes should have no negative impacts on the experience.

Patch Changes

Updated dependencies [65d3425]
- @astrojs/language-server @2.9.0

`v0.5.10`

Compare Source

Patch Changes

9ca368b: Update to the latest version of Volar. This release should fix some of the caching issues that has crept up recently
Updated dependencies [9ca368b]
Updated dependencies [d57daad]
Updated dependencies [b166787]
Updated dependencies [eb49fb2]
- @astrojs/language-server @2.8.4

`v0.5.9`

Compare Source

Patch Changes

f1447ef: chore: Update volar-service-prettier. This is only an internal refactor and there should be no visible changes.
Updated dependencies [f1447ef]
- @astrojs/language-server @2.8.1

`v0.5.8`

Compare Source

Patch Changes

85b42dc: Update to the latest version of Volar. This release fixes a few issues such as missing Prettier crashing the language server in some cases, resolutions not working correctly inside TSX files, and more.
Updated dependencies [85b42dc]
- @astrojs/language-server @2.8.0

`v0.5.7`

Compare Source

Patch Changes

1b68dfb: Improves descriptions for attributes specific to Astro (is:raw, set:html, etc.)
Updated dependencies [2bad6a8]
Updated dependencies [1b68dfb]
- @astrojs/language-server @2.7.7

`v0.5.6`

Compare Source

Patch Changes

fe6165b: Makes astro check --tsconfig understand relative file names
Updated dependencies [fe6165b]
- @astrojs/language-server @2.7.6

withastro/astro (@astrojs/mdx)

`v2.3.1`

Compare Source

Patch Changes

#10754 3e7a12c8532411e580fcfdb8445cad8fc8499291 Thanks @rishi-raj-jain! - Fixes an issue where images in MDX required a relative specifier (e.g. ./)

Now, you can use the standard ![](img.png) syntax in MDX files for images colocated in the same folder: no relative specifier required!

There is no need to update your project; your existing images will still continue to work. However, you may wish to remove any relative specifiers from these MDX images as they are no longer necessary:
```
- ![A cute dog](./dog.jpg)
+ ![A cute dog](dog.jpg)

```
#10770 88ee63a3ba4488c60348cb821034e6d4a057efd0 Thanks @bluwy! - Removes internal MDX processor on buildEnd to free up memory

`v2.3.0`

Compare Source

Minor Changes

#10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

This change is in line with Astro's Node.js support policy.

Patch Changes

Updated dependencies [ccafa8d230f65c9302421a0ce0a0adc5824bfd55]:
- @astrojs/markdown-remark @5.1.0

`v2.2.4`

Compare Source

Patch Changes

#10673 db7f9c87035a0de780536d95cdd9facff00c3c08 Thanks @bluwy! - Removes unnecessary internal recmaInjectImportMetaEnv plugin

Minor Changes

#10104 a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18 Thanks @remcohaszing! - Changes Astro's internal syntax highlighting to use rehype plugins instead of remark plugins. This provides better interoperability with other rehype plugins that deal with code blocks, in particular with third party syntax highlighting plugins and rehype-mermaid.

This may be a breaking change if you are currently using:
- a remark plugin that relies on nodes of type html
- a rehype plugin that depends on nodes of type raw.
Please review your rendered code samples carefully, and if necessary, consider using a rehype plugin that deals with the generated element nodes instead. You can transform the AST of raw HTML strings, or alternatively use hast-util-to-html to get a string from a raw node.

Patch Changes

Updated dependencies [c081adf998d30419fed97d8fccc11340cdc512e0, 5a9528741fa98d017b269c7e4f013058028bdc5d, a31bbd7ff8f3ec62ee507f72d1d25140b82ffc18]:
- @astrojs/markdown-remark @4.3.0

withastro/astro (@astrojs/preact)

`v3.5.0`

Compare Source

Minor Changes

#11234 4385bf7 Thanks @ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

This new function should be preferred when using the Container API in environments like on-demand pages:

import type { APIRoute } from 'astro';
import { experimental_AstroContainer } from 'astro/container';
import reactRenderer from '@&#8203;astrojs/react/server.js';
import vueRenderer from '@&#8203;astrojs/vue/server.js';
import ReactComponent from '../components/button.jsx';
import VueComponent from '../components/button.vue';

// MDX runtime is contained inside the Astro core
import mdxRenderer from 'astro/jsx/server.js';

// In case you need to import a custom renderer
import customRenderer from '../renderers/customRenderer.js';

export const GET: APIRoute = async (ctx) => {
  const container = await experimental_AstroContainer.create();
  container.addServerRenderer({ renderer: reactRenderer });
  container.addServerRenderer({ renderer: vueRenderer });
  container.addServerRenderer({ renderer: customRenderer });
  // You can pass a custom name too
  container.addServerRenderer({
    name: 'customRenderer',
    renderer: customRenderer,
  });
  const vueComponent = await container.renderToString(VueComponent);
  return await container.renderToResponse(Component);
};

`v3.4.0`

Compare Source

Minor Changes

#11144 803dd80 Thanks @ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import ReactWrapper from '../src/components/ReactWrapper.astro';
import { loadRenderers } from 'astro:container';
import { getContainerRenderer } from '@&#8203;astrojs/react';

test('ReactWrapper with react renderer', async () => {
  const renderers = await loadRenderers([getContainerRenderer()]);
  const container = await AstroContainer.create({
    renderers,
  });
  const result = await container.renderToString(ReactWrapper);

  expect(result).toContain('Counter');
  expect(result).toContain('Count: <!-- -->5');
});

`v3.3.0`

Compare Source

Minor Changes

#10938 fd508a0 Thanks @florian-lefebvre! - Adds a devtools option

You can enable Preact devtools in development by setting devtools: true in your preact() integration config:

import { defineConfig } from 'astro/config';
import preact from '@&#8203;astrojs/preact';

export default defineConfig({
  integrations: [preact({ devtools: true })],
});

`v3.2.0`

Compare Source

Minor Changes

#10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

This change is in line with Astro's Node.js support policy.

`v3.1.2`

Compare Source

Patch Changes

#10585 ad50784adc6f262fc563999e97df3a5dc9087c88 Thanks @rschristian! - Fixes (theoretical) edge case in Preact integration's JSX aliases

withastro/astro (@astrojs/rss)

`v4.0.7`

Compare Source

Patch Changes

#11299 8ce66f2 Thanks @ematipico! - Fixes an issue where the pagesGlobToRssItems returned an incorrect type for items

`v4.0.6`

Compare Source

Patch Changes

#11050 841df1f Thanks @mingjunlu! - Fixes an issue where trailing slash is not removed even if the trailingSlash option is set to false.

withastro/astro (@astrojs/sitemap)

`v3.1.6`

Compare Source

Patch Changes

#11263 7d59750 Thanks @wackbyte! - Refactor to use Astro's integration logger for logging

`v3.1.5`

Compare Source

Patch Changes

#10779 cefeadf Thanks @adrianlyjak! - Fixes false positives for status code routes like 404 and 500 when generating sitemaps.

`v3.1.4`

Compare Source

Patch Changes

#10772 0e22462d1534afc8f7bb6782f86db680c7a5f245 Thanks @gislerro! - Fixes an issue where the root url does not follow the trailingSlash config option

`v3.1.3`

Compare Source

Patch Changes

#10795 1ce22881c657becf0397b83ac393fb5d2399104c Thanks @bluwy! - Improves performance when generating the sitemap data

`v3.1.2`

Compare Source

Patch Changes

#10557 5f7e9c47e01116f6ec74b33770f480404680956a Thanks @mingjunlu! - Fixes an issue where the base path is missing in sitemap-index.xml.

withastro/astro (astro)

`v4.11.3`

Compare Source

Patch Changes

#11347 33bdc54 Thanks @bluwy! - Fixes installed packages detection when running astro check
#11327 0df8142 Thanks @ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when using pnpm as package manager.

`v4.11.2`

Compare Source

Patch Changes

#11335 4c4741b Thanks @ematipico! - Reverts #11292, which caused a regression to the input type
#11326 41121fb Thanks @florian-lefebvre! - Fixes a case where running astro sync when using the experimental astro:env feature would fail if environment variables were missing
#11338 9752a0b Thanks @zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent in rtl and ltr layouts
#11331 f1b78a4 Thanks @bluwy! - Removes resolve package and simplify internal resolve check
#11339 8fdbf0e Thanks @matthewp! - Remove non-fatal errors from telemetry

Previously we tracked non-fatal errors in telemetry to get a good idea of the types of errors that occur in astro dev. However this has become noisy over time and results in a lot of data that isn't particularly useful. This removes those non-fatal errors from being tracked.

`v4.11.1`

Compare Source

Patch Changes

#11308 44c61dd Thanks @ematipico! - Fixes an issue where custom 404.astro and 500.astro were not returning the correct status code when rendered inside a rewriting cycle.
#11302 0622567 Thanks @martrapp! - Fixes an issue with the view transition router when redirecting to an URL with different origin.
Updated dependencies [b6afe6a, 41064ce]:
- @astrojs/markdown-remark @5.1.1
- @astrojs/internal-helpers @0.4.1

`v4.11.0`

Compare Source

Minor Changes

#11197 4b46bd9 Thanks @braebo! - Adds ShikiTransformer support to the <Code /> component with a new transformers prop.

Note that transformers only applies classes and you must provide your own CSS rules to target the elements of your code block.

`v4.10.3`

Compare Source

Patch Changes

#11213 94ac7ef Thanks @florian-lefebvre! - Removes the PUBLIC_ prefix constraint for astro:env public variables
#11213 94ac7ef Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

Server secrets specified in the schema must now be imported from astro:env/server. Using getSecret() is no longer required to use these environment variables in your schema:
```
- import { getSecret } from 'astro:env/server'
- const API_SECRET = getSecret("API_SECRET")
+ import { API_SECRET } from 'astro:env/server'
```
Note that using getSecret() with these keys is still possible, but no longer involves any special handling and the raw value will be returned, just like retrieving secrets not specified in your schema.

#11234 4385bf7 Thanks @ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

This new function should be preferred when using the Container API in environments like on-demand pages:

import type { APIRoute } from 'astro';
import { experimental_AstroContainer } from 'astro/container';
import reactRenderer from '@&#8203;astrojs/react/server.js';
import vueRenderer from '@&#8203;astrojs/vue/server.js';
import ReactComponent from '../components/button.jsx';
import VueComponent from '../components/button.vue';

// MDX runtime is contained inside the Astro core
import mdxRenderer from 'astro/jsx/server.js';

// In case you need to import a custom renderer
import customRenderer from '../renderers/customRenderer.js';

export const GET: APIRoute = async (ctx) => {
  const container = await experimental_AstroContainer.create();
  container.addServerRenderer({ renderer: reactRenderer });
  container.addServerRenderer({ renderer: vueRenderer });
  container.addServerRenderer({ renderer: customRenderer });
  // You can pass a custom name too
  container.addServerRenderer({
    name: 'customRenderer',
    renderer: customRenderer,
  });
  const vueComponent = await container.renderToString(VueComponent);
  return await container.renderToResponse(Component);
};

#11249 de60c69 Thanks @markgaze! - Fixes a performance issue with JSON schema generation
#11242 e4fc2a0 Thanks @ematipico! - Fixes a case where the virtual module astro:container wasn't resolved
#11236 39bc3a5 Thanks @ascorbic! - Fixes a case where symlinked content collection directories were not correctly resolved
#11258 d996db6 Thanks @ascorbic! - Adds a new error RewriteWithBodyUsed that throws when Astro.rewrite is used after the request body has already been read.
#11243 ba2b14c Thanks @V3RON! - Fixes a prerendering issue for libraries in node_modules when a folder with an underscore is in the path.
#11244 d07d2f7 Thanks @ematipico! - Improves the developer experience of the custom 500.astro page in development mode.

Before, in development, an error thrown during the rendering phase would display the default error overlay, even when users had the 500.astro page.

Now, the development server will display the 500.astro and the original error is logged in the console.
#11240 2851b0a Thanks @ascorbic! - Ignores query strings in module identifiers when matching ".astro" file extensions in Vite plugin
#11245 e22be22 Thanks @bluwy! - Refactors prerendering chunk handling to correctly remove unused code during the SSR runtime

`v4.10.2`

Compare Source

Patch Changes

#11231 58d7dbb Thanks @ematipico! - Fixes a regression for getViteConfig, where the inline config wasn't merged in the final config.
#11228 1e293a1 Thanks @ascorbic! - Updates getCollection() to always return a cloned array
#11207 7d9aac3 Thanks @ematipico! - Fixes an issue in the rewriting logic where old data was not purged during the rewrite flow. This caused some false positives when checking the validity of URL path names during the rendering phase.
#11189 75a8fe7 Thanks @ematipico! - Improve error message when using getLocaleByPath on path that doesn't contain any locales.

#11195 0a6ab6f Thanks @florian-lefebvre! - Adds support for enums to astro:env

You can now call envField.enum:

import { defineConfig, envField } from 'astro/config';

export default defineConfig({
  experimental: {
    env: {
      schema: {
        API_VERSION: envField.enum({
          context: 'server',
          access: 'secret',
          values: ['v1', 'v2'],
        }),
      },
    },
  },
});

#11210 66fc028 Thanks @matthewp! - Close the iterator only after rendering is complete

#11195 0a6ab6f Thanks @florian-lefebvre! - Adds additional validation options to astro:env

astro:env schema datatypes string and number now have new optional validation rules:

import { defineConfig, envField } from 'astro/config';

export default defineConfig({
  experimental: {
    env: {
      schema: {
        FOO: envField.string({
          // ...
          max: 32,
          min: 3,
          length: 12,
          url: true,
          includes: 'foo',
          startsWith: 'bar',
          endsWith: 'baz',
        }),
        BAR: envField.number({
          // ...
          gt: 2,
          min: 3,
          lt: 10,
          max: 9,
          int: true,
        }),
      },
    },
  },
});

#11211 97724da Thanks @matthewp! - Let middleware handle the original request URL
#10607 7327c6a Thanks @frankbits! - Fixes an issue where a leading slash created incorrect conflict resolution between pages generated from static routes and catch-all dynamic routes

`v4.10.1`

Compare Source

Patch Changes

#11198 8b9a499 Thanks @florian-lefebvre! - Fixes a case where astro:env getSecret would not retrieve environment variables properly in dev and build modes
#11206 734b98f Thanks @florian-lefebvre! - BREAKING CHANGE to the experimental astro:env feature only

Updates the adapter astro:env entrypoint from astro:env/setup to astro/env/setup
#11205 8c45391 Thanks @Nin3lee! - Fixes a typo in the config reference

`v4.10.0`

Compare Source

Minor Changes

#10974 2668ef9 Thanks @florian-lefebvre! - Adds experimental support for the astro:env API.

The astro:env API lets you configure a type-safe schema for your environment variables, and indicate whether they should be available on the server or the client. Import and use your defined variables from the appropriate /client or /server module:

`v4.9.3`

Compare Source

Patch Changes

#11171 ff8004f Thanks @Princesseuh! - Guard globalThis.astroAsset usage in proxy code to avoid errors in wonky situations
#11178 1734c49 Thanks @theoephraim! - Improves isPromise utility to check the presence of then on an object before trying to access it - which can cause undesired side-effects on Proxy objects
#11183 3cfa2ac Thanks @66Leo66! - Suggest pnpm dlx instead of pnpx in update check.
#11147 2d93902 Thanks @kitschpatrol! - Fixes invalid MIME types in Picture source elements for jpg and svg extensions, which was preventing otherwise valid source variations from being shown by the browser
#11141 19df89f Thanks @ematipico! - Fixes an internal error that prevented the AstroContainer to render the Content component.

You can now write code similar to the following to render content collections:
```
const entry = await getEntry(collection, slug);
const { Content } = await entry.render();
const content = await container.renderToString(Content);
```
#11170 ba20c71 Thanks @matthewp! - Retain client scripts in content cache

`v4.9.2`

Compare Source

Patch Changes

#11138 98e0372 Thanks @ematipico! - You can now pass props when rendering a component using the Container APIs:

import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import Card from '../src/components/Card.astro';

const container = await AstroContainer.create();
const result = await container.renderToString(Card, {
  props: {
    someState: true,
  },
});

`v4.9.1`

Compare Source

Patch Changes

#11129 4bb9269 Thanks @matthewp! - Prevent errors from adapters when i18n domains is not used

`v4.9.0`

Compare Source

Minor Changes

#11051 12a1bcc Thanks @ematipico! - Introduces an experimental Container API to render .astro components in isolation.

This API introduces three new functions to allow you to create a new container and render an Astro component returning either a string or a Response:
- create(): creates a new instance of the container.
- renderToString(): renders a component and return a string.
- renderToResponse(): renders a component and returns the Response emitted by the rendering phase.
The first supported use of this new API is to enable unit testing. For example, with vitest, you can create a container to render your component with test data and check the result:
```
import { experimental_AstroContainer as AstroContainer } from 'astro/container';
import { expect, test } from 'vitest';
import Card from '../src/components/Card.astro';

test('Card with slots', async () => {
  const container = await AstroContainer.create();
  const result = await container.renderToString(Card, {
    slots: {
      default: 'Card content',
    },
  });

  expect(result).toContain('This is a card');
  expect(result).toContain('Card content');
});
```
For a complete reference, see the Container API docs.

For a feature overview, and to give feedback on this experimental API, see the Container API roadmap discussion.
#11021 2d4c8fa Thanks @ematipico! - The CSRF protection feature that was introduced behind a flag in v4.6.0 is no longer experimental and is available for general use.

To enable the stable version, add the new top-level security option in astro.config.mjs. If you were previously using the experimental version of this feature, also delete the experimental flag:
```
export default defineConfig({
-  experimental: {
-    security: {
-      csrfProtection: {
-        origin: true
-      }
-    }
-  },
+  security: {
+    checkOrigin: true
+  }
})
```
Enabling this setting performs a check that the "origin" header, automatically passed by all modern browsers, matches the URL sent by each Request.

This check is executed only for pages rendered on demand, and only for the requests POST, PATCH, DELETE and PUT with one of the following "content-type" headers: 'application/x-www-form-urlencoded', 'multipart/form-data', 'text/plain'.

If the "origin" header doesn't match the pathname of the request, Astro will return a 403 status code and won't render the page.

For more information, see the security configuration docs.
#11022 be68ab4 Thanks @ematipico! - The i18nDomains routing feature introduced behind a flag in v3.4.0 is no longer experimental and is available for general use.

This routing option allows you to configure different domains for individual locales in entirely server-rendered projects using the @astrojs/node or @astrojs/vercel adapter with a site configured.

If you were using this feature, please remove the experimental flag from your Astro config:
```
import { defineConfig } from 'astro'

export default defineConfig({
-  experimental: {
-    i18nDomains: true,
-  }
})
```
If you have been waiting for stabilization before using this routing option, you can now do so.

Please see the internationalization docs for more about this feature.

#11071 8ca7c73 Thanks @bholmesdev! - Adds two new functions experimental_getActionState() and experimental_withState() to support the React 19 useActionState() hook when using Astro Actions. This introduces progressive enhancement when calling an Action with the withState() utility.

This example calls a like action that accepts a postId and returns the number of likes. Pass this action to the experimental_withState() function to apply progressive enhancement info, and apply to useActionState() to track the result:

import { actions } from 'astro:actions';
import { experimental_withState } from '@&#8203;astrojs/react/actions';

export function Like({ postId }: { postId: string }) {
  const [state, action, pending] = useActionState(
    experimental_withState(actions.like),
    0 // initial likes
  );

  return (
    <form action={action}>
      <input type="hidden" name="postId" value={postId} />
      <button disabled={pending}>{state} ❤️</button>
    </form>
  );
}

You can also access the state stored by useActionState() from your action handler. Call experimental_getActionState() with the API context, and optionally apply a type to the result:

import { defineAction, z } from 'astro:actions';
import { experimental_getActionState } from '@&#8203;astrojs/react/actions';

export const server = {
  like: defineAction({
    input: z.object({
      postId: z.string(),
    }),
    handler: async ({ postId }, ctx) => {
      const currentLikes = experimental_getActionState<number>(ctx);
      // write to database
      return currentLikes + 1;
    },
  }),
};

#11101 a6916e4 Thanks @linguofeng! - Updates Astro's code for adapters to use the header x-forwarded-for to initialize the clientAddress.

To take advantage of the new change, integration authors must upgrade the version of Astro in their adapter peerDependencies to 4.9.0.

#11071 8ca7c73 Thanks @bholmesdev! - Adds compatibility for Astro Actions in the React 19 beta. Actions can be passed to a form action prop directly, and Astro will automatically add metadata for progressive enhancement.

import { actions } from 'astro:actions';

function Like() {
  return (
    <form action={actions.like}>
      {/* auto-inserts hidden input for progressive enhancement */}
      <button type="submit">Like</button>
    </form>
  );
}

Patch Changes

#11088 9566fa0 Thanks @bholmesdev! - Allow actions to be called on the server. This allows you to call actions as utility functions in your Astro frontmatter, endpoints, and server-side UI components.

Import and call directly from astro:actions as you would for client actions:

`v4.8.7`

Compare Source

Patch Changes

#11073 f5c8fee Thanks @matthewp! - Prevent cache content from being left in dist folder

When contentCollectionsCache is enabled temporary cached content is copied into the outDir for processing. This fixes it so that this content is cleaned out, along with the rest of the temporary build JS.
#11054 f6b171e Thanks @bholmesdev! - Respect error status when handling Actions with a progressive fallback.
#11092 bfe9c73 Thanks @duckycoding-dev! - Change slot attribute of IntrinsicAttributes to match the definition of HTMLAttributes's own slot attribute of type string | undefined | null
#10875 b5f95b2 Thanks @W1M0R! - Fixes a typo in a JSDoc annotation
#11111 [`a

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 bot force-pushed the renovate/site-non-major branch 7 times, most recently from 0464262 to f7343e8 Compare March 6, 2024 03:42

renovate bot force-pushed the renovate/site-non-major branch 7 times, most recently from bc9799c to 8253a3a Compare March 13, 2024 14:17

renovate bot force-pushed the renovate/site-non-major branch 7 times, most recently from 0375ee4 to c5c0497 Compare March 20, 2024 22:03

renovate bot force-pushed the renovate/site-non-major branch 4 times, most recently from 46517b2 to 520bb67 Compare March 28, 2024 20:32

renovate bot force-pushed the renovate/site-non-major branch 5 times, most recently from 6ff5a89 to 258ffa0 Compare April 4, 2024 18:36

renovate bot force-pushed the renovate/site-non-major branch 3 times, most recently from 616ff10 to 66d84fb Compare April 25, 2024 13:32

renovate bot force-pushed the renovate/site-non-major branch 3 times, most recently from fb48661 to 59c5b37 Compare May 9, 2024 13:01

renovate bot force-pushed the renovate/site-non-major branch 5 times, most recently from 2f29449 to 627b1df Compare May 15, 2024 21:59

renovate bot force-pushed the renovate/site-non-major branch 5 times, most recently from aed87f1 to a14bc0c Compare May 23, 2024 16:19

renovate bot force-pushed the renovate/site-non-major branch from a14bc0c to be3cf24 Compare May 27, 2024 14:38

renovate bot force-pushed the renovate/site-non-major branch 4 times, most recently from d035f9a to 1ab71f9 Compare June 8, 2024 10:25

renovate bot force-pushed the renovate/site-non-major branch 2 times, most recently from 3ee60fc to ea22165 Compare June 17, 2024 18:08

renovate bot force-pushed the renovate/site-non-major branch 5 times, most recently from 7e1add3 to faec61f Compare June 26, 2024 10:31

fix(deps): update site (non-major)

7145329

renovate bot force-pushed the renovate/site-non-major branch from faec61f to 7145329 Compare June 26, 2024 13:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update site (non-major) #121

fix(deps): update site (non-major) #121

renovate bot commented Feb 26, 2024 •

edited

Loading

fix(deps): update site (non-major) #121

Are you sure you want to change the base?

fix(deps): update site (non-major) #121

Conversation

renovate bot commented Feb 26, 2024 • edited Loading

Release Notes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Minor Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Configuration

renovate bot commented Feb 26, 2024 •

edited

Loading