Prevent bumping peer deps

[bluwy]

Changes

The integrations' astro peer dep ranges has been updating, which is a breaking change. I changed it to an explicit version range instead of workspace: so changeset doesn't bump it now. Works especially in combination of the onlyUpdatePeerDependentsWhenOutOfRange experimental option.

The peer dep ranges are all reset to "astro": "^3.0.0"

Testing

Ran pnpm changeset version locally.

Docs

n/a.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a05ee8

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.

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

[natemoo-re]

Oh yikes, good catch!

[ematipico]

This will bite us when we are going to do another major release, and the ranges aren't automatically updated. So if you want to go ahead, we must update our internal documentation and remind us that this is a manual step. Why not use workspace:^3.0.0?

[bluwy]

I'll update the internal docs 👍 workspace:^3.0.0 is currently what's causing the issue and changesets is bumping it every version.

[bluwy]

@ematipico looks like with the onlyUpdatePeerDependentsWhenOutOfRange config, changesets is smart enough to also bump the peer dep whenever we enter prerelease mode or cut a new major, so looks like no additional docs is needed.