Skip to content

Conversation

@marcins
Copy link
Contributor

@marcins marcins commented Oct 20, 2025

Motivation

Apart from slightly faster yarn install speeds, the main benefit for us to upgrading to Yarn v4 is that we can use workspace:* dependencies in package.json files, which simplifies dependency management (especially for "big" PRs when there's a release on the main branch to merge in).

Changes

  • Upgrade the repo to use Yarn v4
  • Fix various small issues

The bulk of the change is changing explicit versions of workspace dependencies in package.json to workspace:*.

Checklist

  • Testing a dev release bump in AFM
  • Existing or new tests cover this change
  • There is a changeset for this change, or one is not required
  • Added documentation for any new features to the docs/ folder

[no-changeset]: No functional changes

yamadapc and others added 6 commits October 20, 2025 14:44
Try to fix gh actions

Remove GitHub buffer dependency

Not needed since there is no WASM REPL. If it was needed it should point to an
Atlassian repository.

Fix lockfile

remove install-state from vcs

Point everything at NPMJS instead of packages.atlassian.com

Point everything at NPMJS instead of packages.atlassian.com

Fix hardened installs

Fix typescript errors

Run prettier against yarnrc

Fix install state

Fixes
@marcins marcins requested a review from a team as a code owner October 20, 2025 21:01
@changeset-bot
Copy link

changeset-bot bot commented Oct 20, 2025

⚠️ No Changeset found

Latest commit: 8750a7d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

📊 Type Coverage Report

Coverage Comparison

Metric Baseline Current Change
Coverage Percentage 91.93% 91.93% ➡️ 0.00%
Correctly Typed 196,274 196,274 +0
Total Expressions 213,501 213,501 +0
Untyped Expressions 17,227 17,227 +0

Files with Most Type Issues (Top 15)

File Issues Affected Lines
packages/core/integration-tests/test/javascript.ts 983 648
packages/core/integration-tests/test/cache.ts 885 626
packages/core/integration-tests/test/scope-hoisting.ts 623 490
packages/utils/node-resolver-core/test/resolver.ts 476 177
packages/core/integration-tests/test/html.ts 468 294
packages/core/integration-tests/test/sourcemaps.ts 356 176
packages/core/test-utils/src/utils.ts 330 205
packages/core/integration-tests/test/incremental-bundling.ts 298 206
packages/core/core/src/dumpGraphToGraphViz.ts 251 108
packages/core/integration-tests/test/output-formats.ts 227 161
packages/transformers/webextension/src/WebExtensionTransformer.ts 210 80
packages/core/integration-tests/test/react-refresh.ts 197 71
packages/core/integration-tests/test/css-modules.ts 191 107
packages/core/core/src/requests/TargetRequest.ts 190 133
packages/core/integration-tests/test/babel.ts 187 115

This report was generated by the Type Coverage GitHub Action

@mattcompiles
Copy link
Contributor

@marcins Have you validated that the changesets release handles this correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants