chore(tool/cmd/syncversion): rm syncversion tool (#4966)

Remove `syncversion` tool because legacylibrarian release stage will
sync library version from state.yaml to librarian.yaml (#4961).

No need to run this tool manually.

chore(python): update sdk.yaml with non-default release levels (#4850)

The language-default release level is often different to the current
Python library release level, as determined by the existing
.repo-metadata.json files. The sdk.yaml file is updated to reflect the
current state of play in google-cloud-python, so that after migration
we still generate the same .repo-metadata.json files.

Also adds google/maps/geocode/v4 to the allow-list, as that's now in
google-cloud-python.

Fixes #4847.

feat: enable google-cloud-visionai-v1 for Rust (#4806)

fix(internal/legacylibrarian): allow parsing commits with no space (#…

…4061)

A recent commit in googleapis had no space after the conventional commit
sperator. We need to be able to parse a commit like this.

Fixes: #4060

fix(internal/legacylibrarian): use 'release:failed' label upon failure (

#4017)

When a release fails to process we don't want to indefinitely retry
processing that pull request. We will instead now mark it as failed so
future searches from our automation don't find the pull request. In
these cases a bug will be opened from a production notification in
Google Cloud which will require an engineer to investigate the failure.

Internal Bug: b/481308012

fix(internal/legacylibrarian): retry on more status codes (#3989)

GitHub had an outage yesterday which was cauing some of our jobs to fail
for a while. While this was happening I noticed we were getting and not
honoring these two statuses from thier serveres.

Internal Bug: b/483305951

feat(internal/librarian): find release commits and libraries released (…

…#3642)

Add findReleasedLibraries, which determines which libraries are released
by a specific commit.

Add findLatestReleaseCommit, which looks back in git history to find the
first commit to release either any library, or just a specified library.

These will be used by the tag and publish commands.

Fixes #3597

chore: librarian release pull request: 20251120T152217Z (#2982)

PR created by the Librarian CLI to initialize a release. Merging this PR
will auto trigger a release.

Librarian Version: not available
Language Image:
us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/librarian-release-container:latest
<details><summary>librarian: 0.7.0</summary>

##
[0.7.0](v0.6.0...v0.7.0)
(2025-11-20)

### Features

* add command execution package with logging (#2968)
([12f4e94](12f4e949))

* add branch support to RepositoryConfig (#2906)
([2cab5d6](2cab5d65))

* add image sha as a config in repositories config (#2954)
([3d1f537](3d1f5375))

* add initial config (#2965)
([502b063](502b063c))

* add fetch package (#2964)
([53de44d](53de44d8))

* parse gapic_metadata for API version release notes (#2815)
([7ee0328](7ee03283))

* onboard 25 repositories to automation for publish-release (#2907)
([87fae04](87fae04a))

* add version command (#2894)
([8f85be0](8f85be09))

* add RequireCommand test helper (#2978)
([a820a71](a820a710))

* add initial command (#2961)
([c959aea](c959aeae))

* add `stage-release` command (#2902)
([ee05006](ee050065))

### Bug Fixes

* require git v2.28.0 (#2963)
([265ee47](265ee47f))

* enums referenced outside the package (#2952)
([7331816](73318169))

</details>

doc(librarian): document current behavior when using local repo with …

…push flag (#2885)

Documents current behavior that when using local repo, Librarian will
branch-off the checked-out branch for commits, but will attempt to
create PR against main branch if `push` flag is set.

Add clarification to `branch` flag description that it is ignored with
local repo.

Fixes #2877

chore: revert Librarian CLI release to pre-major release (#2898)

We prematurely released 1.0.0 version of Librarian CLI, when it is not
yet stable. We have retracted this release and will continue on with pre
1.0 releases, starting with 0.6.0.