Changesets Setup

[brophdawg11]

Minor updates to do some local testing of the changesets flow. With these changes you can:

# Enter prerelease mode and commit changes
pnpm exec changeset pre enter pre
git add .
git commit -a -m "Enter prerelease mode"

# Run version command to bump to 7.0.0-pre.0 and add entries to CHANGELOG's
export GITHUB_TOKEN="....."
pnpm exec changeset version
git add .
git commit -m "Prerelease"

# Run a dry publish run to see what would be published to npm
pnpm -r publish --dry-run --publish-branch brophdawg11/changesets

Everything looks good to me in that flow, so with these changes I think we'll be in good shape when it comes time to do a prerelease

[changeset-bot]

⚠️ No Changeset found

Latest commit: d3ef3ff

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

[brophdawg11]

Needed these to be in the 6.x range so they'll bump to 7.x when changesets does a major bump

[brophdawg11]

This is going away eventually so can just make it 6.x for now

[markdalgleish]

To keep things simple do we want to keep this version fixed with the other packages then?

[brophdawg11]

Yeah - I guess it could go into the changesets fixed config - but it’ll get deleted from there before we do any v7 pre-releases (along with native/compat/dom) I think so might not ever have a chance to do anything?

[brophdawg11]

Changesets doesn't run if these don't have names/versions

[markdalgleish]

Thanks for catching this.