When adding a new version to an existing Skill, the name is fixed, and you publish a new bundle under a SemVer version number greater than the previous one.

Skill-wide information like the description and tags isn't changed through a version update — it's changed on a separate edit screen instead. Those fields don't appear on the version-update form, but the existing values are kept and submitted along with it.

Release notes are the one field that's never auto-filled. You need to write what changed in this version yourself for it to appear in the version table on the detail page.