Merge to release #39
Merged
Merge to release #39
Conversation
This file contains 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
![the-zazukoian[bot]](https://avatars.githubusercontent.com/in/100144?s=60&v=4){kind=small}
the-zazukoian
bot
force-pushed
the
changeset-release/main
branch
from
8d302c0
to
4fcbe09
Compare
the-zazukoian
bot
force-pushed
the
changeset-release/main
branch
from
4fcbe09
to
ee76865
Compare
ludovicm67
approved these changes
Jun 3, 2024
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 main, this PR will be updated.
Releases
[email protected]
Minor Changes
1b8342c: Add xkey support in order to support tag-based invalidation.
The backend can now send a
xkeyheader with a value that will be used to tag the cache entry.This tag can be used to invalidate the cache entry by sending a
PURGErequest with thexkeyheader set to the same value like this:curl -sL -X PURGE -H 'xkey: TAG_VALUE' http://varnish-endpoint/Doing this will remove all cache entries that have the same tag value.