Use workspace:* identifiers for workspace dependencies

[JoviDeCroock]

Problem

Internal package dependencies use explicit semver ranges, which complicates publishing — especially with staged publishing and minimumReleaseAge, where a just-published internal version isn't resolvable yet. It also caused workspace installs to resolve internal packages from the registry (e.g. @prefresh/core@1.5.4) instead of linking the local workspace packages.

Changes

• Switch all internal dependencies and devDependencies in @prefresh/nollup, @prefresh/vite, @prefresh/web-dev-server, and @prefresh/webpack to workspace:*, which pnpm replaces with the exact local version at publish time. The lockfile now links these as workspace packages.
• peerDependencies on @prefresh/babel-plugin keep their loose ranges, since the workspace protocol would pin them to exact versions on publish.
• Bump pnpm to 11.3.0 in the test workflow to match the release workflow, as the lockfile is now written in the newer format.

The test fixtures need no changes: yarn's resolutions field overrides the workspace:* ranges before resolution, as already shown by the existing @prefresh/rolldown dependency.

Fixes #616

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1e01509

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