chore(release): version packages#1
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
December 4, 2025 01:56
6757da8 to
f835df2
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
3 times, most recently
from
December 16, 2025 02:18
02d6b4a to
5dacc6b
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
6 times, most recently
from
January 13, 2026 01:55
1a2b5c2 to
4040476
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
January 23, 2026 01:58
600707a to
9a89b29
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
January 29, 2026 02:05
2ac244e to
c63fa71
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
3 times, most recently
from
March 20, 2026 02:21
b5cc022 to
9beb3c1
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
5 times, most recently
from
March 29, 2026 01:56
a123fa5 to
721b42c
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
March 31, 2026 02:32
721b42c to
06f5e7c
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
April 3, 2026 03:04
06f5e7c to
c9a2feb
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
4 times, most recently
from
May 22, 2026 03:26
0c743ea to
591e33a
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
4 times, most recently
from
June 11, 2026 04:41
ab96bc8 to
8fb2fa0
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
3 times, most recently
from
July 14, 2026 02:38
909cd03 to
0d44261
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
2 times, most recently
from
July 23, 2026 03:32
299bfb8 to
d034551
Compare
github-actions
Bot
force-pushed
the
changeset-release/master
branch
from
July 24, 2026 03:35
d034551 to
7124ae9
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 master, this PR will be updated.
Releases
ctx7@0.5.6
Patch Changes
ghdirectly instead of through a shell. The shell wrapper (cmd.exe /d /s /con Windows) caused endpoint protection tools such as Microsoft Defender for Endpoint to raise a "Suspicious Node.js process behavior" alert duringctx7 setup.ctx7 setupskill install failing with "fetch failed" when the GitHub git tree API (api.github.com) is blocked or unreachable. Skill download now falls back to fetching the singleSKILL.mddirectly fromraw.githubusercontent.com— the URL the docs API already resolves — so setup succeeds in environments where only the docs/raw hosts are reachable.@upstash/context7-mcp@3.2.5
Patch Changes
undicito 7 and require Node.js >= 20.18.1. On Node 26+ (internal undici 8) the bundled undici 6setGlobalDispatcherwrote a global-dispatcher symbol the built-infetchno longer reads, soHTTPS_PROXYand custom-CA settings were silently ignored and requests failed withENOTFOUNDbehind CONNECT proxies. undici 7 writes both symbols, restoring proxy and CA support. Node 18 is no longer supported (EOL; undici 7 requires Node >= 20.18.1).