Version Packages #698
Merged
Version Packages #698
Conversation
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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
@bedframe/[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^
[email protected]
Patch Changes
7f8128b: add temp legacy config.
Temporary workaround for upstream (crxjs) issue:
change to Vite CORS policies in the dev server:
"
In Vite 6.0.8 and below, WebSocket server was able to connect from any web pages. However,
that could be exploited by a malicious web page.
In Vite 6.0.9+, the WebSocket server now requires a token to connect from a web page.
But this may break some plugins and frameworks that connects to the WebSocket server
on their own. Enabling this option will make Vite skip the token check.
We do not recommend enabling this option unless you are sure that you are fine with
that security weakness.
"
^^^