nibtime / next-safe-middleware

Strict CSP (Content-Security-Policy) for Next.js hybrid apps https://web.dev/strict-csp/
https://next-safe-middleware.vercel.app
MIT License
79 stars 20 forks source link

Version Packages #65

Closed github-actions[bot] closed 2 years ago

github-actions[bot] commented 2 years ago

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

@next-safe/middleware@0.10.0

Minor Changes

docs@0.2.0

Minor Changes

Patch Changes

e2e@0.6.2

Patch Changes

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
docs-next-safe-middleware ✅ Ready (Inspect) Visit Preview Sep 1, 2022 at 11:52PM (UTC)
e2e-next-safe-middleware ✅ Ready (Inspect) Visit Preview Sep 1, 2022 at 11:52PM (UTC)
nibtime commented 2 years ago

@middlebaws @shamilik

this upcoming version should work with Firefox and Safari (>= 15.4)

Shamilik commented 2 years ago

Both previews works fine on Safari. Thanks @nibtime!

nibtime commented 2 years ago

Awesome, I manually stress-tested it again with Chrome and Firefox both with e2e and docs apps and couldn't yield any errors.

Sometimes, there a random Partytown (worker scripts) type error logs to console on page loads. But I can also produce it without this package and the test worker script runs without problems, so I suppose it's not that bad and a problem of Next, if any.

Screenshot ![2022-08-02 22_24_15](https://user-images.githubusercontent.com/52962482/182466667-2d38ec0f-a5ad-40dd-aeae-7327d1d43955.png)

So I am going to release it now, 0.10.0 is on NPM. I also recommend to upgrade Next to 12.2.4 as soon as possible, as it fixes routing bugs related to middleware

Once #66 is done, I will tackle #42. Writing the code for this was quite a hassle, there are many strange edge cases all over the place. That's why I won't release a major version before there are automated e2e tests against regressions.