[WIP] When opening a pull request that changes a package, a changeset needs to be created. If the change is a bugfix, a patch version is appropriate; if it's a new feature it should be minor. (For breaking changes it should be major but you will rarely...

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original description:

When opening a pull request that changes a package, a changeset needs to be created. If the change is a bugfix, a patch version is appropriate; if it's a new feature it should be minor. (For breaking changes it should be major but you will rarely be asked to work on a breaking change.)

To create one, run pnpm changeset in the project root and follow the prompts. The changeset message should be a short, one-line description summarising the change, and should begin with fix: or feat: or chore: as appropriate.

Can you update .github/copilot-instructions.md to add this information in such a way that you always remember to add a changeset with pull requests?

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c82a26c

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](https://github.com/sveltejs/kit/new/copilot/fix-8a9c5c5d-56e3-471b-ac40-67f3f149fb36?filename=.changeset/rude-lizards-applaud.md&value=---%0A%0A---%0A%0A%5BWIP%5D%20When%20opening%20a%20pull%20request%20that%20changes%20a%20package%2C%20a%20changeset%20needs%20to%20be%20created.%20If%20the%20change%20is%20a%20bugfix%2C%20a%20%60patch%60%20version%20is%20appropriate%3B%20if%20it's%20a%20new%20feature%20it%20should%20be%20%60minor%60.%20(For%20breaking%20changes%20it%20should%20be%20%60major%60%20but%20you%20will%20rarely...%0A)

[Rich-Harris]

ah whoops, this was already done in #14206