What should you write when changing a package?

A changeset is a small note that names the package, the size of its version change and what users should know. Keep it in the project. For a package with several contributors, the notes give the release reviewer a list of what changed across different edits.

Does preparing new versions publish the packages?

Versioning writes the next versions and changelog. Publishing is separate. The GitHub Action can support a release pull request, and a configured publish workflow can publish afterward. Check which action version matches your Changesets version and who may merge or trigger publication.

What files should travel with the project?

Keep changeset notes, package files, configuration and changelog in Git. The open-source tool can prepare a release without its own hosting service. Your workflow runner and package registry have separate limits and permissions.

Which change belongs in the next package release?

Write a fictional bug fix for one library and a test-only change for another. Sketch the release notes and version changes you expect.

Choose the package and bump
Name the package whose users see the fix and give it a patch note.
Review before publishing
List the files that should change. Keep publishing out of the practice run.