Skip to content

Pin dependencies #20049

@Lms24

Description

@Lms24

Description

We should start pinning all our dependencies more aggressively, given the recent supply chain attacks and other problems arising from bumping dependencies. Some things to consider

  • latest/next/canary tests need to be excempt from pinning
  • we keep some dependency versions ^-declared on purpose so that users can potentially install more recent (minor/patch) versions of the package and deduplicate the installed version. This concerns our bundler plugins mostly. A couple of OTel packages have the same strategy. We should re-evaluate if this makes sense on a package-by-package level.

Metadata

Metadata

Assignees

No one assigned
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions