You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We may want to check how the recent releases of the deno_* crates could impact our permissions system, and whether integrating them can result in improvements in ergonomics or functionality for extensions over the current versions.
There are some breaking changes in a few types (BootstrapOptions, WorkerOptions and PermissionsOptions) and some of their associated functions.
IIRC, for all 0.x versions, any semver-minor bump is treated as a potentially breaking change, and only patch updates are considered non-breaking, and with that rationale it does make sense not to bump minor versions. I found that this is most often the case, with crates starting to be non-breaking on the minor patch only once their 1.x releases.
(I tried manually performing the above updates and, indeed, there were breaking changes in the Deno API).
Activity
kylewillmon commentedon Oct 3, 2022
Hmm... I thought dependabot would alert us about these sorts of updates...
Maybe ignoring
semver-minorupdates means that 0.x dependencies are never bumped?andreaphylum commentedon Oct 3, 2022
IIRC, for all 0.x versions, any semver-minor bump is treated as a potentially breaking change, and only patch updates are considered non-breaking, and with that rationale it does make sense not to bump minor versions. I found that this is most often the case, with crates starting to be non-breaking on the minor patch only once their 1.x releases.
(I tried manually performing the above updates and, indeed, there were breaking changes in the Deno API).
Update deno dependencies
Update deno dependencies
Update deno dependencies (#723)