[icanhasmath]

Follow-up to #3867, from testing the 0.48.2-RC2 Windows build: changing the namespace in the state publish editor was refused, and nothing said in advance which fields were fixed.

Changes

• Default namespace: without --namespace (or a namespace in the --meta file), state publish --build now uses private/<org>/python when the source directory has a pyproject.toml. Otherwise it still uses private/<org>.

• Namespace edits: a new ingredient's namespace can now be changed in the editor. --build writes the name and version into the package, but not the namespace. The new namespace gets the same checks as --namespace:

  • it can't be empty
  • with --build, it must be under the project's organization
  • the version must not already exist in it

  If it fails a check, the previous namespace is put back, the user's other edits are kept, and the reason is shown. With --edit the namespace still can't be changed, because it identifies the ingredient being revised.

• Fixed fields stated up front: with --build or --edit, the confirmation prompt and the editor notice say which fields can't be changed and why. If one is changed anyway, the error names that field (e.g. "The name can't be changed at this point, because it was already built into the package") instead of "name, namespace or version".

• No help comments in the meta data: the confirmation preview and the editor no longer show a comment on every field (# The name of the ingredient, ...). They now show the same plain yaml as saved meta files and state export ingredient-meta. The fields are described in a table in the publish guide instead. The yaml-comment module, and maruel/natural which only it used, are removed from go.mod and vendor/.

• Description in export and --edit:

  • state export ingredient-meta left the description empty, although it is published. The description belongs to the ingredient, not the version, so export now fetches it from there.
  • state publish --edit no longer refuses a description that differs on an existing version. The confirmation shows the current description and says the change is ignored, and the other edits can still be published. The description is still left out of the request for a revision, because the platform rejects it.
  • Authors on an existing version are still refused.

Testing

• The new tests in confirm_test.go cover the default namespace, a namespace edit that is kept, each check that puts the old namespace back, and the fixed-field errors for --build and --edit. Tests also cover the preview having no comments, the exported description, and an ignored description change. Each test fails when its fix is reverted.
• The readme and changelog are updated.

🤖 Generated with Claude Code