Publish packages #32
Merged
Publish packages #32
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
github-actions
bot
force-pushed
the
changeset-release/master
branch
from
13b0838
to
9eed4dd
Compare
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
@ducanh2912/next-pwa@8.7.0
Minor Changes
fa08192Thanks @DuCanhGH! - feat(next-pwa, experimental): aggressiveFrontEndNavCachingThis feature, combined with
cacheFrontEndNav, will cache<link rel="stylesheet" href="" />and<script src="" />on frontend navigation. This allowspages which have only been visited through that method to work offline when directly visited.
Frontend navigation caching has also been offloaded to a separate worker with this feature.
docs@1.0.2
Patch Changes
fa08192]: