chore: version packages#68
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 9, 2026 17:55
3364d06 to
20b5aea
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 19, 2026 17:37
20b5aea to
adaf8cc
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 19, 2026 19:58
adaf8cc to
557d390
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 publish to npm yourself or setup this action to publish 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
@dualmark/fastly@0.11.0
Minor Changes
fastly-compute-example@1.0.1
Patch Changes
@dualmark/astro@0.11.0
Patch Changes
@dualmark/converters@0.11.0
Patch Changes
8611bed: Fix the blog converter turning a post's last body line into a heading.
The footer was concatenated directly onto the body with no blank line, so the output ended with
last body line\n---. CommonMark parses a line of text immediately followed by---as a setext H2, which turned the final line of every blog post body into a heading and dropped the intended horizontal rule before the footer links. The body and footer are now separated by a blank line so the---is a thematic break.@dualmark/nextjs@0.11.0
Patch Changes
@dualmark/nuxt@0.11.0
Patch Changes
3501da1: Set the required headers on the Nuxt 406 response.
When a request explicitly excluded both
text/htmlandtext/markdown, the Nuxt adapter returnednew Response('Not Acceptable', { status: 406 })with no headers. The spec (content-negotiation.md section 4) requires a 406 to setVary: Accept, and it should carry aContent-Typeand a body listing the supported types. The 406 now matches the other adapters:Content-Type: text/plain; charset=utf-8,Vary: Accept, and a supported-types body. This applies to both the generated collection middleware and the runtime middleware.Updated dependencies [8611bed]
@dualmark/sveltekit@0.11.0
Patch Changes
dualmark-example-astro-blog@0.0.11
Patch Changes
dualmark-example-astro-cloudflare-full@0.0.11
Patch Changes
dualmark-example-netlify-edge@0.0.3
Patch Changes
dualmark-example-nextjs-app-router@0.0.10
Patch Changes
dualmark-example-sanity-astro@0.0.2
Patch Changes
dualmark-example-sveltekit-blog@0.0.4
Patch Changes