chore: avoid an unwanted mdx major bump#16977
Merged
Merged
Conversation
|
ematipico
approved these changes
Jun 5, 2026
Merged
matthewp
pushed a commit
that referenced
this pull request
Jun 8, 2026
* fix(errors): correct param key in getStaticPaths error-doc examples (slug → id) (#16976) * fix(cloudflare): defer createApp/setGetEnv in fetch.ts to avoid circular import crash (#16956) (#16968) * fix(fetch): sync request.url with forwarded headers in FetchState (#16947) * fix(fetch): sync request.url with forwarded headers in FetchState (#16945) * chore: improve tests and solution --------- Co-authored-by: astrobot-houston <fred+astrobot@astro.build> * chore: avoid an unwanted mdx major bump (#16977) * chore(renovate): bump max memory (#16993) --------- Co-authored-by: Minh Lê <115204145+DucMinhNe@users.noreply.github.com> Co-authored-by: Houston (Bot) <108291165+astrobot-houston@users.noreply.github.com> Co-authored-by: Emanuele Stoppa <estoppa@cloudflare.com> Co-authored-by: astrobot-houston <fred+astrobot@astro.build> Co-authored-by: Florian Lefebvre <contact@florian-lefebvre.dev>
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
2 participants
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.
Changes
Unblock #16972 (review)
Before this PR, Changesets will make the following change in #16972:
{ "name": "@astrojs/markdown-satteri", - "version": "0.2.2", + "version": "0.3.0", }{ "name": "@astrojs/mdx", - "version": "6.0.2", + "version": "7.0.0", "peerDependencies": { - "@astrojs/markdown-satteri": "0.2.2" + "@astrojs/markdown-satteri": "0.3.0" } }After this PR,
changesetswill make the following change:{ "name": "@astrojs/markdown-satteri", - "version": "0.2.2", + "version": "0.3.0", }{ "name": "@astrojs/mdx", - "version": "6.0.2", + "version": "6.0.3", "peerDependencies": { "@astrojs/markdown-satteri": "0.3.0" } }This is just a workaround. We can revert the change in this PR and reuse
workspace:*once we have merged Changeset release and published new versions.Testing
Tested locally with
./node_modules/.bin/changeset versionto ensure that Changeset won't crash and won't bump@astrojs/mdxto a major version after my change.Green CI. In other words, tools like
pnpmandturboaccept"@astrojs/markdown-satteri": "0.3.0"in thepeerDependencies, even thoughpackages/markdown/satteri/package.jsononly has"version": "0.2.2".Docs
N/A