Open
Conversation
varlock-bot
force-pushed
the
changeset-release/main
branch
from
03cd9f8 to
5d3ae1f
Compare
commit: |
varlock-bot
force-pushed
the
changeset-release/main
branch
from
5d3ae1f to
711889e
Compare
varlock-bot
force-pushed
the
changeset-release/main
branch
from
711889e to
e2c57c3
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
1 participant
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
varlock@0.4.2
Patch Changes
#385
5890ee6- fix:patchGlobalResponsebrokefetch()responses failinginstanceof Responsechecks. After patchingglobalThis.ResponsewithVarlockPatchedResponse, nativefetch()still returned the originalResponseinstances, causing SvelteKit SSR endpoints to throw "handler should return a Response object". AddedSymbol.hasInstancetoVarlockPatchedResponseso native responses pass the check.#384
0642185- Fix telemetry disable command showing incorrect success message#387
64c8ba9- fix: auto trigger type generation invarlock run(unless auto=false flag is used)