[ci] release#11186
Merged
Merged
Conversation
70c99aa to
b4d0cc1
Compare
b4d0cc1 to
4394951
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
astro@4.10.0
Minor Changes
#10974
2668ef9Thanks @florian-lefebvre! - Adds experimental support for theastro:envAPI.The
astro:envAPI 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/clientor/servermodule:To define the data type and properties of your environment variables, declare a schema in your Astro config in
experimental.env.schema. TheenvFieldhelper allows you define your variable as a string, number, or boolean and pass properties in an object:There are three kinds of environment variables, determined by the combination of
context(clientorserver) andaccess(privateorpublic) settings defined in yourenv.schema:Public client variables: These variables end up in both your final client and server bundles, and can be accessed from both client and server through the
astro:env/clientmodule:Public server variables: These variables end up in your final server bundle and can be accessed on the server through the
astro:env/servermodule:Secret server variables: These variables are not part of your final bundle and can be accessed on the server through the
getSecret()helper function available from theastro:env/servermodule:Note: Secret client variables are not supported because there is no safe way to send this data to the client. Therefore, it is not possible to configure both
context: "client"andaccess: "secret"in your schema.To learn more, check out the documentation.
Patch Changes
#11192
58b10a0Thanks @liruifengv! - Improves DX by throwing the originalAstroUserErrorwhen an error is thrown inside a.mdxfile.#11136
35ef53cThanks @ematipico! - Errors that are emitted during a rewrite are now bubbled up and shown to the user. A 404 response is not returned anymore.#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.#11144
803dd80Thanks @ematipico! - BREAKING CHANGE to the experimental Container API onlyChanges the type of the
renderersoption of theAstroContainer::createfunction and adds a dedicated functionloadRenderers()to load the rendering scripts from renderer integration packages (@astrojs/react,@astrojs/preact,@astrojs/solid-js,@astrojs/svelte,@astrojs/vue,@astrojs/lit, and@astrojs/mdx).You no longer need to know the individual, direct file paths to the client and server rendering scripts for each renderer integration package. Now, there is a dedicated function to load the renderer from each package, which is available from
getContainerRenderer():import { experimental_AstroContainer as AstroContainer } from 'astro/container'; import ReactWrapper from '../src/components/ReactWrapper.astro'; import { loadRenderers } from "astro:container"; import { getContainerRenderer } from "@astrojs/react"; test('ReactWrapper with react renderer', async () => { + const renderers = await loadRenderers([getContainerRenderer()]) - const renderers = [ - { - name: '@astrojs/react', - clientEntrypoint: '@astrojs/react/client.js', - serverEntrypoint: '@astrojs/react/server.js', - }, - ]; const container = await AstroContainer.create({ renderers, }); const result = await container.renderToString(ReactWrapper); expect(result).toContain('Counter'); expect(result).toContain('Count: <!-- -->5'); });The new
loadRenderers()helper function is available fromastro:container, a virtual module that can be used when running the Astro container insidevite.#11136
35ef53cThanks @ematipico! - It's not possible anymore to useAstro.rewrite("/404")inside static pages. This isn't counterproductive because Astro will end-up emitting a page that contains the HTML of 404 error page.It's still possible to use
Astro.rewrite("/404")inside on-demand pages, or pages that opt-out from prerendering.#11191
6e29a17Thanks @matthewp! - Fixes a case whereAstro.urlwould be incorrect when havingbuild.formatset to'preserve'in the Astro config#11182
40b0b4dThanks @ematipico! - Fixes an issue whereAstro.rewritewasn't carrying over the body of aRequestin on-demand pages.#11194
97fbe93Thanks @ematipico! - Fixes an issue where the functiongetViteConfigwasn't returning the correct merged Astro configuration@astrojs/lit@4.2.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/mdx@3.1.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/preact@3.4.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/react@3.5.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/solid-js@4.3.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/svelte@5.5.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.@astrojs/vue@4.4.0
Minor Changes
#11144
803dd80Thanks @ematipico! - The integration now exposes a function calledgetContainerRenderer, that can be used inside the Container APIs to load the relative renderer.