api-specs
api-specs copied to clipboard
fix(deps): update astro
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| @astrojs/starlight (source) | ^0.24.4 -> ^0.25.5 |
||||
| astro (source) | ^4.11.1 -> ^4.13.4 |
Release Notes
withastro/starlight (@astrojs/starlight)
v0.25.5
Patch Changes
-
#2171
c8258d7Thanks @delucis! - Improves build performance slightly for bigger sites -
#2199
91557fdThanks @connorjs! - Adds Azure DevOps (azureDevOps) icon for use in social links.
v0.25.4
Patch Changes
-
#2155
8bed886Thanks @delucis! - Improves page load performance on slower devices -
#2167
9ac7725Thanks @delucis! - Fixes an issue detecting the built-in locale when running Starlight in a web container environment on Firefox -
#2166
4f12049Thanks @delucis! - Updates@astrojs/mdx,@astrojs/sitemap,astro-expressive-code,unified, andvfiledependencies to the latest version
v0.25.3
Patch Changes
-
#2154
0b381d5Thanks @mktbsh! - Updates<head>logic to deduplicate<link rel="canonical">tags. This means that custom canonicals set via frontmatter now override the default canonical generated by Starlight. -
#2157
6757d97Thanks @astrobot-houston! - Updates file tree icon mapping to correctly map.cjsand.mjsextensions in several contexts -
#2156
904ad47Thanks @delucis! - Fixes builds for projects with a space in their pathname -
#2137
703903bThanks @cevdetardaharan! - Removestwitter:titleandtwitter:descriptionmeta tags from<head>
v0.25.2
Patch Changes
-
#2126
ada51eeThanks @essential-randomness! - Adds support for markdown formatting in aside titles -
#2135
9bbb969Thanks @oluwatobiss! - Adds Pinterest social icon
v0.25.1
Patch Changes
-
#2122
359a642Thanks @HiDeoo! - Fixes an i18n configuration issue for multilingual sites when using Astro’si18nconfig withprefixDefaultLocaleset tofalse. -
#2107
61e223bThanks @sanabel-al-firdaws! - Updates Arabic UI translations -
#2105
81f8a2cThanks @delucis! - Fixes an edge case in custom pagination link processingCustom link values for
prev/nextin page frontmatter are now always used as authored. Previously this was not the case in some edge cases such as for the first and final pages in the sidebar. -
#2119
464685aThanks @evadecker! - Improves styling of<hr>,<blockquote>, and<code>within asides
v0.25.0
Minor Changes
-
#2025
47f32c1Thanks @HiDeoo! - Removes the/search shortcut for accessibility reasons.⚠️ Potentially breaking change: The
search.shortcutLabelUI string has been removed. If you were using this string in your custom UI, you will need to update your code. -
#2064
c5b47cbThanks @SnowDingo! - Improves styling of Markdown tables to work better in different contexts, including against different background colours like when used in asides. -
#2031
2bab648Thanks @delucis! - Makes sidebar entry parsing stricter in Starlight config⚠️ Potentially breaking change: Previously Starlight would accept a sidebar entry that matched one of its expected shapes, even if it included additional properties. For example, including both
linkanditemswas considered valid, withitemsbeing ignored. Now, it is an error to include more than one oflink,items, orautogeneratein a sidebar entry.If you see errors after updating, look for sidebar entries in the Starlight configuration in
astro.config.mjsthat include too many keys and remove the one that was previously ignored. -
#1874
eeba06eThanks @lorenzolewis! - Adds a new syntax for specifying sidebar link items for internal linksYou can now specify an internal page using only its slug, either as a string, or as an object with a
slugproperty:starlight({ title: 'Docs with easier sidebars', sidebar: ['getting-started', { slug: 'guides/installation' }], });Starlight will use the linked page’s frontmatter to configure the sidebar link.
Patch Changes
- #2081
f0181d2Thanks @andrii-bodnar! - Updates the Ukrainian UI translations
v0.24.5
Patch Changes
-
#2062
5ac0ac6Thanks @evadecker! - Increase theme and language select inline padding -
#2056
87e9ad0Thanks @HiDeoo! - Fixes an issue preventing remark plugins injected by Starlight plugins to handle Markdown text and leaf directives. -
#2063
3ee1a94Thanks @delucis! - TranslatefileTree.directoryandaside.*UI string into Norwegian (Bokmål). -
#2054
dbfd3eeThanks @HiDeoo! - Fixes an issue when using the<StarlightPage>component in a custom page with a user-definedsrcDirconfiguration.
withastro/astro (astro)
v4.13.4
Patch Changes
-
#11678
34da907Thanks @ematipico! - Fixes a case where omitting a semicolon and line ending with carriage return - CRLF - in theprerenderoption could throw an error. -
#11535
932bd2eThanks @matthewp! - Encrypt server island propsServer island props are now encrypted with a key generated at build-time. This is intended to prevent accidentally leaking secrets caused by exposing secrets through prop-passing. This is not intended to allow a server island to be trusted to skip authentication, or to protect against any other vulnerabilities other than secret leakage.
See the RFC for an explanation: https://github.com/withastro/roadmap/blob/server-islands/proposals/server-islands.md#props-serialization
-
#11655
dc0a297Thanks @billy-le! - Fixes Astro Actionsinputvalidation when usingdefaultvalues with a form input. -
#11689
c7bda4cThanks @ematipico! - Fixes an issue in the Astro actions, where the size of the generated cookie was exceeding the size permitted by theSet-Cookieheader.
v4.13.3
Patch Changes
-
#11653
32be549Thanks @florian-lefebvre! - Updatesastro:envdocs to reflect current developments and usage guidance -
#11658
13b912aThanks @bholmesdev! - FixesorThrow()type when calling an Action without aninputvalidator. -
#11603
f31d466Thanks @bholmesdev! - Improves user experience when render an Action result from a form POST request:- Removes "Confirm post resubmission?" dialog when refreshing a result.
- Removes the
?_astroAction=NAMEflag when a result is rendered.
Also improves the DX of directing to a new route on success. Actions will now redirect to the route specified in your
actionstring on success, and redirect back to the previous page on error. This follows the routing convention of established backend frameworks like Laravel.For example, say you want to redirect to a
/successroute whenactions.signupsucceeds. You can add/successto youractionstring like so:<form method="POST" action={'/success' + actions.signup}></form>- On success, Astro will redirect to
/success. - On error, Astro will redirect back to the current page.
You can retrieve the action result from either page using the
Astro.getActionResult()function.
Note on security
This uses a temporary cookie to forward the action result to the next page. The cookie will be deleted when that page is rendered.
⚠ The action result is not encrypted. In general, we recommend returning minimal data from an action handler to a) avoid leaking sensitive information, and b) avoid unexpected render issues once the temporary cookie is deleted. For example, a login function may return a user's session id to retrieve from your Astro frontmatter, rather than the entire user object.
v4.13.2
Patch Changes
-
#11648
589d351Thanks @bholmesdev! - Fixes unexpected error when refreshing a POST request from a form using Actions. -
#11600
09ec2caThanks @ArmandPhilippot! - DeprecatesgetEntryBySlugandgetDataEntryByIdfunctions exported byastro:contentin favor ofgetEntry. -
#11593
81d7150Thanks @bholmesdev! - Adds support forDate(),Map(), andSet()from action results. See devalue for a complete list of supported values.Also fixes serialization exceptions when deploying Actions with edge middleware on Netlify and Vercel.
-
#11617
196092aThanks @abubakriz! - Fix toolbar audit incorrectly flagging images as above the fold. -
#11634
2716f52Thanks @bholmesdev! - Fixes internal server error when calling an Astro Action without arguments on Vercel. -
#11628
9aaf58cThanks @madbook! - Ensures consistent CSS chunk hashes across different environments
v4.13.1
Patch Changes
-
#11584
a65ffe3Thanks @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
Minor Changes
-
#11507
a62345fThanks @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
e5e2d3eThanks @alexanderniebuhr! - Theexperimental.contentCollectionJsonSchemafeature 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 insrc/content/config.tsusing a library calledzod-to-json-schema.This feature requires you to manually set your schema's file path as the value for
$schemain 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.schemassetting, 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
45ad326Thanks @ematipico! - Theexperimental.rewritingfeature introduced behind a flag in v4.8.0 is no longer experimental and is available for general use.Astro.rewrite()andcontext.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.astropage component to display a different page's content, such as fallback localized content:
v4.12.3
Patch Changes
-
#11509
dfbca06Thanks @bluwy! - Excludes hoisted scripts and styles from Astro components imported with?urlor?raw -
#11561
904f1e5Thanks @ArmandPhilippot! - Uses the correct pageSize default inpage.sizeJSDoc comment -
#11571
1c3265aThanks @bholmesdev! - BREAKING CHANGE to the experimental Actions API only. Install the latest@astrojs/reactintegration 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
Patch Changes
-
#11505
8ff7658Thanks @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
026e8baThanks @sarah11918! - Fixes typo in documenting theslot="fallback"attribute for Server Islands experimental feature. -
#11508
ca335e1Thanks @cramforce! - Escapes HTML in serialized props -
#11501
4db78aeThanks @martrapp! - Adds the missing export for accessing thegetFallback()function of the client site router.
v4.12.1
Patch Changes
-
#11486
9c0c849Thanks @ematipico! - Adds a new function calledaddClientRendererto the Container API.This function should be used when rendering components using the
client:*directives. TheaddClientRendererAPI must be used after the use of theaddServerRenderer:const container = await experimental_AstroContainer.create(); container.addServerRenderer({ renderer }); container.addClientRenderer({ name: '@​astrojs/react', entrypoint: '@​astrojs/react/client.js' }); const response = await container.renderToResponse(Component); -
#11500
4e142d3Thanks @Princesseuh! - Fixes inferRemoteSize type not working -
#11496
53ccd20Thanks @alfawal! - Hide the dev toolbar onwindow.print()(CTRL + P)
v4.12.0
Minor Changes
-
#11341
49b5145Thanks @madcampos! - Adds support for Shiki'sdefaultColoroption.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: falsein 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
Patch Changes
-
#11459
bc2e74dThanks @mingjunlu! - Fixes false positive audit warnings on elements with the role "tabpanel". -
#11472
cb4e6d0Thanks @delucis! - Avoids targeting all files in thesrc/directory for eager optimization by Vite. After this change, only JSX, Vue, Svelte, and Astro components get scanned for early optimization. -
#11387
b498461Thanks @bluwy! - Fixes prerendering not removing unused dynamic imported chunks -
#11437
6ccb30eThanks @NuroDev! - Fixes a case where Astro's configexperimental.env.schemakeys did not allow numbers. Numbers are still not allowed as the first character to be able to generate valid JavaScript identifiers -
#11439
08baf56Thanks @bholmesdev! - Expands theisInputError()utility fromastro:actionsto 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
0e66849Thanks @FugiTech! - Fixes an issue where using .nullish() in a formdata Astro action would always parse as a string -
#11438
619f07dThanks @bholmesdev! - Exposes utility types fromastro:actionsfor thedefineActionhandler (ActionHandler) and theActionErrorcode (ActionErrorCode). -
#11456
17e048dThanks @RickyC0626! - Fixesastro dev --openunexpected behavior that spawns a new tab every time a config file is saved -
#11337
0a4b31fThanks @florian-lefebvre! - Adds a new propertyexperimental.env.validateSecretsto allow validating private variables on the server.By default, this is set to
falseand 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
ea4bc04Thanks @bholmesdev! - Expose newActionReturnTypeutility fromastro:actions. This infers the return type of an action by passingtypeof actions.nameas a type argument. This example defines alikeaction that returnslikesas 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
7dca68fThanks @bholmesdev! - Fixesastro:actionsautocompletion for thedefineActionacceptproperty -
#11455
645e128Thanks @florian-lefebvre! - Improvesastro:envinvalid variables errors
v4.11.5
Patch Changes
- #11408
b9e906fThanks @matthewp! - Revert change to how boolean attributes work
v4.11.4
Patch Changes
-
#11362
93993b7Thanks @ematipico! - Fixes an issue where creating manually the i18n middleware could break the logic of the functions of the virtual moduleastro:i18n -
#11349
98d9ce4Thanks @ematipico! - Fixes an issue where Astro didn't throw an error whenAstro.rewritewas used without providing the experimental flag -
#11352
a55ee02Thanks @ematipico! - Fixes an issue where the rewrites didn't update the status code when using manual i18n routing. -
#11388
3a223b4Thanks @mingjunlu! - Adjusts the color of punctuations in error overlay. -
#11369
e6de11fThanks @bluwy! - Fixes attribute rendering for non-boolean attributes with boolean values
v4.11.3
Patch Changes
-
#11347
33bdc54Thanks @bluwy! - Fixes installed packages detection when runningastro check -
#11327
0df8142Thanks @ematipico! - Fixes an issue with the container APIs where a runtime error was thrown during the build, when usingpnpmas package manager.
v4.11.2
Patch Changes
-
#11335
4c4741bThanks @ematipico! - Reverts #11292, which caused a regression to the input type -
#11326
41121fbThanks @florian-lefebvre! - Fixes a case where runningastro syncwhen using the experimentalastro:envfeature would fail if environment variables were missing -
#11338
9752a0bThanks @zaaakher! - Fixes svg icon margin in devtool tooltip title to look coherent inrtlandltrlayouts -
#11331
f1b78a4Thanks @bluwy! - Removesresolvepackage and simplify internal resolve check -
#11339
8fdbf0eThanks @matthewp! - Remove non-fatal errors from telemetryPreviously 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.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.
Deploy Preview for openpodcastapi ready!
| Name | Link |
|---|---|
| Latest commit | b63fa7760bb7879e4443849e754ae331706f4e86 |
| Latest deploy log | https://app.netlify.com/sites/openpodcastapi/deploys/66f67fd4ef50ee0008d91ac9 |
| Deploy Preview | https://deploy-preview-94--openpodcastapi.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
@Sporiff I checked the preview and I also read the changelog, however you are more into astro/starlight, would you mind having a look here as well? Especially since its a quite big version jump