For the rare cases where a generated change should result in a major version bump, Librarian will support a manual override mechanism. A library maintainer can specify the next desired version in the .librarian/config.yaml file.
For example:
libraries:
- id: google-cloud-example
next_version: 2.0.0
During a release, if this configuration is present, Librarian will use 2.0.0 as the version for the google-cloud-example library. Librarian will ignore this value if the library's last-released version is already higher than the one specified.
Alternatively, librarian release init command will allow explicitly specifying the release version, when asking to release a single library from the repository. The specified version will take precedence over the one in the .librarian/config.yaml.
Ref: go/librarian:commits
For the rare cases where a generated change should result in a major version bump, Librarian will support a manual override mechanism. A library maintainer can specify the next desired version in the
.librarian/config.yamlfile.For example:
During a release, if this configuration is present, Librarian will use
2.0.0as the version for thegoogle-cloud-examplelibrary. Librarian will ignore this value if the library's last-released version is already higher than the one specified.Alternatively,
librarian release initcommand will allow explicitly specifying the release version, when asking to release a single library from the repository. The specified version will take precedence over the one in the.librarian/config.yaml.Ref: go/librarian:commits