panva
commented
2 months ago Hi @iuioiua
I would add v2.x stable when it releases. Unstable releases would need continue-on-error so that I am not bombarded by notifications from, well, unstable releases, which kinda defeats the point you're making.
issues that users may run into when migrating from Deno 1 to 2
jose for Deno only uses Web Platform APIs, if there are breakages in those then failing WPTs will present themselves.
If you want early insight into Deno's popular packages and include jose, all you have to do in Deno's CI, or something similar to Node's CITGM, is
- fetch the latest tag (those contain a dist folder)
- npm install (to get some of the test suite's dependencies)
- run the
tap:denopackage.json script
iuioiua
This PR enables Deno canary in CI, which currently is the same as enabling Deno 2.0.0-rc.0. This has the obvious benefit of future-proofing this package for Deno 2, but also gives us (Deno) early insight into any issues that users may run into when migrating from Deno 1 to 2.