fix(deps): update astro monorepo #302

renovate · 2024-08-04T08:27:53Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@astrojs/sitemap (source)	`3.1.5` -> `3.1.6`
astro (source)	`4.10.2` -> `4.13.1`

Release Notes

withastro/astro (@astrojs/sitemap)

`v3.1.6`

Compare Source

Patch Changes

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

withastro/astro (astro)

`v4.13.1`

Compare Source

Patch Changes

#11584 a65ffe3 Thanks @bholmesdev! - Removes async local storage dependency from Astro Actions. This allows Actions to run in Cloudflare and Stackblitz without opt-in flags or other configuration.

This also introduces a new convention for calling actions from server code. Instead of calling actions directly, you must wrap function calls with the new Astro.callAction() utility.

callAction() is meant to trigger an action from server code. getActionResult() usage with form submissions remains unchanged.

`v4.13.0`

Compare Source

Minor Changes

#11507 a62345f Thanks @ematipico! - Adds color-coding to the console output during the build to highlight slow pages.

Pages that take more than 500 milliseconds to render will have their build time logged in red. This change can help you discover pages of your site that are not performant and may need attention.
#11379 e5e2d3e Thanks @alexanderniebuhr! - The experimental.contentCollectionJsonSchema feature introduced behind a flag in v4.5.0 is no longer experimental and is available for general use.

If you are working with collections of type data, Astro will now auto-generate JSON schema files for your editor to get IntelliSense and type-checking. A separate file will be created for each data collection in your project based on your collections defined in src/content/config.ts using a library called zod-to-json-schema.

This feature requires you to manually set your schema's file path as the value for $schema in each data entry file of the collection:
```
{
  "$schema": "../../../.astro/collections/authors.schema.json",
  "name": "Armand",
  "skills": ["Astro", "Starlight"]
}
```
Alternatively, you can set this value in your editor settings. For example, to set this value in VSCode's json.schemas setting, provide the path of files to match and the location of your JSON schema:
```
{
  "json.schemas": [
    {
      "fileMatch": ["/src/content/authors/**"],
      "url": "./.astro/collections/authors.schema.json"
    }
  ]
}
```
If you were previously using this feature, please remove the experimental flag from your Astro config:
```
import { defineConfig } from 'astro'

export default defineConfig({
-  experimental: {
-    contentCollectionJsonSchema: true
-  }
})
```
If you have been waiting for stabilization before using JSON Schema generation for content collections, you can now do so.

Please see the content collections guide for more about this feature.
#11542 45ad326 Thanks @ematipico! - The experimental.rewriting feature introduced behind a flag in v4.8.0 is no longer experimental and is available for general use.

Astro.rewrite() and context.rewrite() allow you to render a different page without changing the URL in the browser. Unlike using a redirect, your visitor is kept on the original page they visited.

Rewrites can be useful for showing the same content at multiple paths (e.g. /products/shoes/men/ and /products/men/shoes/) without needing to maintain two identical source files.

Rewrites are supported in Astro pages, endpoints, and middleware.

Return Astro.rewrite() in the frontmatter of a .astro page component to display a different page's content, such as fallback localized content:

`v4.12.3`

Compare Source

Patch Changes

#11509 dfbca06 Thanks @bluwy! - Excludes hoisted scripts and styles from Astro components imported with ?url or ?raw
#11561 904f1e5 Thanks @ArmandPhilippot! - Uses the correct pageSize default in page.size JSDoc comment
#11571 1c3265a Thanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest @astrojs/react integration as well if you're using React 19 features.

Make .safe() the default return value for actions. This means { data, error } will be returned when calling an action directly. If you prefer to get the data while allowing errors to throw, chain the .orThrow() modifier.
```
import { actions } from 'astro:actions';

// Before
const { data, error } = await actions.like.safe();
// After
const { data, error } = await actions.like();

// Before
const newLikes = await actions.like();
// After
const newLikes = await actions.like.orThrow();
```

`v4.12.2`

Compare Source

Patch Changes

#11505 8ff7658 Thanks @ematipico! - Enhances the dev server logging when rewrites occur during the lifecycle or rendering.

The dev server will log the status code before and after a rewrite:
```
08:16:48 [404] (rewrite) /foo/about 200ms
08:22:13 [200] (rewrite) /about 23ms
```
#11506 026e8ba Thanks @sarah11918! - Fixes typo in documenting the slot="fallback" attribute for Server Islands experimental feature.
#11508 ca335e1 Thanks @cramforce! - Escapes HTML in serialized props
#11501 4db78ae Thanks @martrapp! - Adds the missing export for accessing the getFallback() function of the client site router.

`v4.12.1`

Compare Source

Patch Changes

#11486 9c0c849 Thanks @ematipico! - Adds a new function called addClientRenderer to the Container API.

This function should be used when rendering components using the client:* directives. The addClientRenderer API must be used
after the use of the addServerRenderer:

const container = await experimental_AstroContainer.create();
container.addServerRenderer({ renderer });
container.addClientRenderer({ name: '@&#8203;astrojs/react', entrypoint: '@&#8203;astrojs/react/client.js' });
const response = await container.renderToResponse(Component);

#11500 4e142d3 Thanks @Princesseuh! - Fixes inferRemoteSize type not working
#11496 53ccd20 Thanks @alfawal! - Hide the dev toolbar on window.print() (CTRL + P)

`v4.12.0`

Compare Source

Minor Changes

#11341 49b5145 Thanks @madcampos! - Adds support for Shiki's defaultColor option.

This option allows you to override the values of a theme's inline style, adding only CSS variables to give you more flexibility in applying multiple color themes.

Configure defaultColor: false in your Shiki config to apply throughout your site, or pass to Astro's built-in <Code> component to style an individual code block.
```
import { defineConfig } from 'astro/config';
export default defineConfig({
  markdown: {
    shikiConfig: {
      themes: {
        light: 'github-light',
        dark: 'github-dark',
      },
      defaultColor: false,
    },
  },
});
```

`v4.11.6`

Compare Source

Patch Changes

#11459 bc2e74d Thanks @mingjunlu! - Fixes false positive audit warnings on elements with the role "tabpanel".
#11472 cb4e6d0 Thanks @delucis! - Avoids targeting all files in the src/ directory for eager optimization by Vite. After this change, only JSX, Vue, Svelte, and Astro components get scanned for early optimization.
#11387 b498461 Thanks @bluwy! - Fixes prerendering not removing unused dynamic imported chunks
#11437 6ccb30e Thanks @NuroDev! - Fixes a case where Astro's config experimental.env.schema keys did not allow numbers. Numbers are still not allowed as the first character to be able to generate valid JavaScript identifiers

#11439 08baf56 Thanks @bholmesdev! - Expands the isInputError() utility from astro:actions to accept errors of any type. This should now allow type narrowing from a try / catch block.

// example.ts
import { actions, isInputError } from 'astro:actions';

try {
  await actions.like(new FormData());
} catch (error) {
  if (isInputError(error)) {
    console.log(error.fields);
  }
}

#11452 0e66849 Thanks @FugiTech! - Fixes an issue where using .nullish() in a formdata Astro action would always parse as a string
#11438 619f07d Thanks @bholmesdev! - Exposes utility types from astro:actions for the defineAction handler (ActionHandler) and the ActionError code (ActionErrorCode).
#11456 17e048d Thanks @RickyC0626! - Fixes astro dev --open unexpected behavior that spawns a new tab every time a config file is saved
#11337 0a4b31f Thanks @florian-lefebvre! - Adds a new property experimental.env.validateSecrets to allow validating private variables on the server.

By default, this is set to false and only public variables are checked on start. If enabled, secrets will also be checked on start (dev/build modes). This is useful for example in some CIs to make sure all your secrets are correctly set before deploying.
```
// astro.config.mjs
import { defineConfig, envField } from 'astro/config';

export default defineConfig({
  experimental: {
    env: {
      schema: {
        // ...
      },
      validateSecrets: true,
    },
  },
});
```

#11443 ea4bc04 Thanks @bholmesdev! - Expose new ActionReturnType utility from astro:actions. This infers the return type of an action by passing typeof actions.name as a type argument. This example defines a like action that returns likes as an object:

// actions/index.ts
import { defineAction } from 'astro:actions';

export const server = {
  like: defineAction({
    handler: () => {
      /* ... */
      return { likes: 42 };
    },
  }),
};

In your client code, you can infer this handler return value with ActionReturnType:

// client.ts
import { actions, ActionReturnType } from 'astro:actions';

type LikesResult = ActionReturnType<typeof actions.like>;
// -> { likes: number }

#11436 7dca68f Thanks @bholmesdev! - Fixes astro:actions autocompletion for the defineAction accept property
#11455 645e128 Thanks @florian-lefebvre! - Improves astro:env invalid variables errors

`v4.11.5`

Compare Source

Patch Changes

#11408 b9e906f Thanks @matthewp! - Revert change to how boolean attributes work

`v4.11.4`

Compare Source

Patch Changes

#11362 93993b7 Thanks @ematipico! - Fixes an issue where creating manually the i18n middleware could break the logic of the functions of the virtual module astro:i18n
#11349 98d9ce4 Thanks @ematipico! - Fixes an issue where Astro didn't throw an error when Astro.rewrite was used without providing the experimental flag
#11352 a55ee02 Thanks @ematipico! - Fixes an issue where the rewrites didn't update the status code when using manual i18n routing.
#11388 3a223b4 Thanks @mingjunlu! - Adjusts the color of punctuations in error overlay.
#11369 e6de11f Thanks @bluwy! - Fixes attribute rendering for non-boolean attributes with boolean values

`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

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 was generated by Mend Renovate. View the repository job log.

cloudflare-workers-and-pages · 2024-08-04T08:28:35Z

Deploying tuhura-tech-website with Cloudflare Pages

Latest commit:	`29c760c`
Status:	🚫 Deploy failed.

View logs

fix(deps): update astro monorepo

29c760c

github-actions bot deployed to tuhura-tech-website (Preview) August 4, 2024 08:28 View deployment

Darkflame72 merged commit e048b85 into main Aug 4, 2024
1 of 2 checks passed

Darkflame72 deleted the renovate/astro-monorepo branch August 4, 2024 08:51

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix(deps): update astro monorepo #302

fix(deps): update astro monorepo #302

renovate bot commented Aug 4, 2024

cloudflare-workers-and-pages bot commented Aug 4, 2024 •

edited

Loading

fix(deps): update astro monorepo #302

fix(deps): update astro monorepo #302

Conversation

renovate bot commented Aug 4, 2024

Release Notes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Configuration

cloudflare-workers-and-pages bot commented Aug 4, 2024 • edited Loading

Deploying tuhura-tech-website with Cloudflare Pages

cloudflare-workers-and-pages bot commented Aug 4, 2024 •

edited

Loading