Skip to content

Bump deno_* crates versions #707

Closed

Description

@andreaphylum

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.

We should evaluate the following updates:

deno_runtime 0.71.0  ->  0.79.0
deno_core    0.145.0 -> 0.153.0
deno_ast     0.17.0  ->  0.19.0

Activity

  1. kylewillmon commented on Oct 3, 2022

    @kylewillmon
    Contributor

    Hmm... I thought dependabot would alert us about these sorts of updates...

    Maybe ignoring semver-minor updates means that 0.x dependencies are never bumped?

  2. andreaphylum commented on Oct 3, 2022

    @andreaphylum
    ContributorAuthor

    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).

  3. added 2 commits that reference this issue on Oct 6, 2022
    deb0643
    93b6394
  4. added a commit that references this issue on Oct 7, 2022
    235c8e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestneeds triageNeeds to be reviewed or assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions