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.
main
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onmain
.Releases
astro@3.0.0-rc.6
Major Changes
#8207
e45f30293
Thanks @natemoo-re! - Change the View Transition built-in animation options.The
transition:animate
valuemorph
has been renamed toinitial
. Also, this is no longer the default animation.If no
transition:animate
directive is specified, your animations will now default tofade
.Astro also supports a new
transition:animate
value,none
. This value can be used on a page's<html>
element to disable animated full-page transitions on an entire page.Minor Changes
#8218
44f7a2872
Thanks @matthewp! - View Transitions unflaggedView Transition support in Astro is now unflagged. For those who have used the experimental feature you can remove the flag in your Astro config:
After removing this flag, please also consult the specific upgrade to v3.0 advice as some API features have changed and you may have breaking changes with your existing view transitions.
See the View Transitions guide to learn how to use the API.
#8181
a8f35777e
Thanks @matthewp! - Finalize View Transition event namesPatch Changes
#8217
c37632a20
Thanks @martrapp! - Specifydata-astro-reload
(no value) on an anchor element to force the browser to ignore view transitions and fall back to default loading.This is helpful when navigating to documents that have different content-types, e.g. application/pdf, where you want to use the build in viewer of the browser.
Example:
<a href='/my.pdf' data-astro-reload>...</a>
#8156
acf652fc1
Thanks @kurtextrem! - The scrollend mechanism is a better way to record the scroll position compared to throttling, so we now use it whenever a browser supports it.#8196
632579dc2
Thanks @bluwy! - Prevent bundling sharp as it errors in runtime#8214
55c10d1d5
Thanks @Princesseuh! - Automatically update user's env.d.ts with the proper types to help out migrating away from assets being experimental@astrojs/rss@3.0.0-rc.2
Major Changes
#8198
cb95aa5f8
Thanks @bluwy! - Update therss()
default export to return aResponse
instead of a simple object, which is deprecated in Astro 3.0. If you were directly returning therss()
result from an endpoint before, this breaking change should not affect you.You can also import
getRssString()
to get the RSS string directly and use it to return your own Response:@astrojs/react@3.0.0-rc.5
Patch Changes
4bd2fac8d
Thanks @bluwy! - Publish missingvnode-children.js
file