withastro/astro (astro)
### [`v4.13.1`](https://togithub.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#4131)
[Compare Source](https://togithub.com/withastro/astro/compare/astro@4.13.0...astro@4.13.1)
##### Patch Changes
- [#11584](https://togithub.com/withastro/astro/pull/11584) [`a65ffe3`](https://togithub.com/withastro/astro/commit/a65ffe314b112213421def26c7cc5b7e7b93558c) Thanks [@bholmesdev](https://togithub.com/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`](https://togithub.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#4130)
[Compare Source](https://togithub.com/withastro/astro/compare/astro@4.12.3...astro@4.13.0)
##### Minor Changes
- [#11507](https://togithub.com/withastro/astro/pull/11507) [`a62345f`](https://togithub.com/withastro/astro/commit/a62345fd182ae4886d586c8406ed8f3e5f942730) Thanks [@ematipico](https://togithub.com/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](https://togithub.com/withastro/astro/pull/11379) [`e5e2d3e`](https://togithub.com/withastro/astro/commit/e5e2d3ed3076f10b4645f011b13888d5fa16e92e) Thanks [@alexanderniebuhr](https://togithub.com/alexanderniebuhr)! - The `experimental.contentCollectionJsonSchema` feature introduced behind a flag in [v4.5.0](https://togithub.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#450) 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`](https://togithub.com/StefanTerdell/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:
```json title="src/content/authors/armand.json" ins={2}
{
"$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](https://code.visualstudio.com/docs/languages/json#\_json-schemas-and-settings), provide the path of files to match and the location of your JSON schema:
```json
{
"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:
```diff
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](https://docs.astro.build/en/guides/content-collections/#enabling-json-schema-generation) for more about this feature.
- [#11542](https://togithub.com/withastro/astro/pull/11542) [`45ad326`](https://togithub.com/withastro/astro/commit/45ad326932971b44630a32d9092c9505f24f42f8) Thanks [@ematipico](https://togithub.com/ematipico)! - The `experimental.rewriting` feature introduced behind a flag in [v4.8.0](https://togithub.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#480) 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:
sindresorhus/globals (globals)
### [`v15.9.0`](https://togithub.com/sindresorhus/globals/compare/v15.8.0...b1d88b841b68e2f56f283140ae5c4b210f39e7dc)
[Compare Source](https://togithub.com/sindresorhus/globals/compare/v15.8.0...v15.9.0)
lint-staged/lint-staged (lint-staged)
### [`v15.2.8`](https://togithub.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md#1528)
[Compare Source](https://togithub.com/lint-staged/lint-staged/compare/v15.2.7...v15.2.8)
##### Patch Changes
- [`f0480f0`](https://togithub.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981) Thanks [@iiroj](https://togithub.com/iiroj)! - In the previous version the native `git rev-parse --show-toplevel` command was taken into use for resolving the current git repo root. This version switched the `--show-toplevel` flag with `--show-cdup`, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js `child_process`. The new flag returns a path relative to the working directory, avoiding the issue.
The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.
remeda/remeda (remeda)
### [`v2.7.0`](https://togithub.com/remeda/remeda/releases/tag/v2.7.0)
[Compare Source](https://togithub.com/remeda/remeda/compare/v2.6.0...v2.7.0)
##### Features
- **chunk:** literal chunk sizes ([#785](https://togithub.com/remeda/remeda/issues/785)) ([785b885](https://togithub.com/remeda/remeda/commit/785b885c72f4cb0d2a2d325ba63d69668ff5c443)), closes [#784](https://togithub.com/remeda/remeda/issues/784)
Configuration
📅 Schedule: Branch creation - "after 3am on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 contains the following updates:
22.0.2->22.1.04.12.3->4.13.115.8.0->15.9.015.2.7->15.2.82.6.0->2.7.0Release Notes
withastro/astro (astro)
### [`v4.13.1`](https://togithub.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#4131) [Compare Source](https://togithub.com/withastro/astro/compare/astro@4.13.0...astro@4.13.1) ##### Patch Changes - [#11584](https://togithub.com/withastro/astro/pull/11584) [`a65ffe3`](https://togithub.com/withastro/astro/commit/a65ffe314b112213421def26c7cc5b7e7b93558c) Thanks [@bholmesdev](https://togithub.com/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`](https://togithub.com/withastro/astro/blob/HEAD/packages/astro/CHANGELOG.md#4130) [Compare Source](https://togithub.com/withastro/astro/compare/astro@4.12.3...astro@4.13.0) ##### Minor Changes - [#11507](https://togithub.com/withastro/astro/pull/11507) [`a62345f`](https://togithub.com/withastro/astro/commit/a62345fd182ae4886d586c8406ed8f3e5f942730) Thanks [@ematipico](https://togithub.com/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](https://togithub.com/withastro/astro/pull/11379) [`e5e2d3e`](https://togithub.com/withastro/astro/commit/e5e2d3ed3076f10b4645f011b13888d5fa16e92e) Thanks [@alexanderniebuhr](https://togithub.com/alexanderniebuhr)! - The `experimental.contentCollectionJsonSchema` feature introduced behind a flag in [v4.5.0](https://togithub.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#450) 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`](https://togithub.com/StefanTerdell/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: ```json title="src/content/authors/armand.json" ins={2} { "$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](https://code.visualstudio.com/docs/languages/json#\_json-schemas-and-settings), provide the path of files to match and the location of your JSON schema: ```json { "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: ```diff 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](https://docs.astro.build/en/guides/content-collections/#enabling-json-schema-generation) for more about this feature. - [#11542](https://togithub.com/withastro/astro/pull/11542) [`45ad326`](https://togithub.com/withastro/astro/commit/45ad326932971b44630a32d9092c9505f24f42f8) Thanks [@ematipico](https://togithub.com/ematipico)! - The `experimental.rewriting` feature introduced behind a flag in [v4.8.0](https://togithub.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md#480) 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:sindresorhus/globals (globals)
### [`v15.9.0`](https://togithub.com/sindresorhus/globals/compare/v15.8.0...b1d88b841b68e2f56f283140ae5c4b210f39e7dc) [Compare Source](https://togithub.com/sindresorhus/globals/compare/v15.8.0...v15.9.0)lint-staged/lint-staged (lint-staged)
### [`v15.2.8`](https://togithub.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md#1528) [Compare Source](https://togithub.com/lint-staged/lint-staged/compare/v15.2.7...v15.2.8) ##### Patch Changes - [`f0480f0`](https://togithub.com/lint-staged/lint-staged/commit/f0480f01b24b9f6443a12515d413a7ba4dda3981) Thanks [@iiroj](https://togithub.com/iiroj)! - In the previous version the native `git rev-parse --show-toplevel` command was taken into use for resolving the current git repo root. This version switched the `--show-toplevel` flag with `--show-cdup`, because on Git installed via MSYS2 the former was returning absolute paths that do not work with Node.js `child_process`. The new flag returns a path relative to the working directory, avoiding the issue. The GitHub Actions workflow has been updated to install Git via MSYS2, to ensure better future compatibility; using the default Git binary in the GitHub Actions runner was working correctly even with MSYS2.remeda/remeda (remeda)
### [`v2.7.0`](https://togithub.com/remeda/remeda/releases/tag/v2.7.0) [Compare Source](https://togithub.com/remeda/remeda/compare/v2.6.0...v2.7.0) ##### Features - **chunk:** literal chunk sizes ([#785](https://togithub.com/remeda/remeda/issues/785)) ([785b885](https://togithub.com/remeda/remeda/commit/785b885c72f4cb0d2a2d325ba63d69668ff5c443)), closes [#784](https://togithub.com/remeda/remeda/issues/784)Configuration
📅 Schedule: Branch creation - "after 3am on Sunday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.