Update publishing.md.

[polina-c]

Add instructions for on-call.

[gemini-code-assist]

Code Review

This pull request adds a new "On-call responsibilities" section to the publishing documentation, outlining weekly tasks for releasing packages and handling 'wip' versions in the changelog. The reviewer suggested improving the Markdown formatting by replacing curly quotes with standard backticks, correcting typos, and fixing minor grammatical issues.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[ditman]

I think having an explicit "-wip" choice makes this process a little bit more complicated; but I guess that's the Dart standard so let's go!

[ditman]

Needing this makes me feel that there's a point in the process that introduces ambiguity when reviewing. Do you think the "-wip" should be just a "escape hatch" when a change really really does not need to be published, that the reviewers can suggest to do?

For example, in flutter/packages, there's the same expectation of "auto-publish after every push", but what this flow calls "-wip" is called "NEXT" there (see this). NEXT changes are not expected to be published at all (and the automation skips them), and only when a real release happens, their changelog entries get merged into that of the release.

[polina-c]

Interesting.

I like the direction.

For me "NEXT" also means some changes.

I like 'noop' more.

And, 'wip' versions still may exist as development artifact, needed for testing.

I will review the doc from this perspective.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:a2ui_core	0.0.1-wip002	ready to publish	a2ui_core-v0.0.1-wip002
package:genai_primitives	0.2.4	ready to publish	genai_primitives-v0.2.4
package:genui	0.9.2	already published at pub.dev
package:genui_a2a	0.9.0	already published at pub.dev
package:json_schema_builder	0.1.5	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.