• Tag per repo: A single release PR will result in a single release tag for the entire repository. This suits languages like Java and C++.
• Tag per library(default): A single release PR can generate multiple, distinct tags, one for each library that has changed. For languages like Go, Librarian will also support defining a release tag template (e.g., policysimulator/v0.4.0) to match their existing conventions necessary for Go releases.

The strategy will be configured at a repository level in the .librarian/config.yaml. This allows a single, atomic release operation to serve the different tagging and versioning schemes required by each language.

To support releasing a single library, Librarian release init command will allow optionally passing a library name and release version. If not provided, all libraries that need releasing will be included in the release PR.

The actual implementation of the strategies will be part of #1009