python-documentai-toolbox: release-please is broken

[daniel-sanche]

https://github.com/googleapis/python-documentai-toolbox is not yet onboarded to librarian, so it still uses release-please for releases. The last release we merged wasn't pushed to pypi, and we had to manually go in and trigger a release job

IIRC, we had the same issue with python-crc32c

Let me know if this is the wrong place to report this, since it's not technically a librarian issue. But I assumed they shared some of the same release infrastructure

[julieqiu]

/cc @bisun-google

[parthea]

This is blocked on #3304. I'll propose a fix

[suztomo]

The last release we merged wasn't pushed to pypi, and we had to manually go in and trigger a release job

The tag regular expression (^v(\d+)\.(\d+)\.(\d+)((a|b|rc)\d+)?(\.dev\d+)?$) in the Louhi flow didn't match the Git tag v0.15.0-alpha. The Louhi flow seems to expect it to have something like v0.15.0a0?

https://pypi.org/project/google-cloud-documentai-toolbox/#history shows 0.15.0a0.

[parthea]

This could be a limitation in the Louhi flow. https://peps.python.org/pep-0440/#pre-release-spelling mentions that alpha is supported and will be "normalized"

Pre-releases allow the additional spellings of alpha, beta, c, pre, and preview for a, b, rc, rc, and rc respectively. This allows versions such as 1.1alpha1, 1.1beta2, or 1.1c3 which normalize to 1.1a1, 1.1b2, and 1.1rc3. In every case the additional spelling should be considered equivalent to their normal forms.

[ldetmer]

If you need to unblock the existing release I believe I can just manually trigger the louhi flow for the merged release commit.

[suztomo]

I think Sanche is not blocked as he was able to trigger the release job manually.

Filed b/470374598 "Resolve the gap in Python repository release tag format in Louhi: "a" v.s. "-alpha".

[daniel-sanche]

Yeah, we're not blocked on this one, this was filed to avoid manual triggers for next time

[parthea]

Releases using librarian will work once #3305 and googleapis/python-documentai-toolbox#392 are merged. b/470374598 will also need to be fixed.

[julieqiu]

@parthea is this issue fixed?

[parthea]

The previous issue #3305 was fixed in librarian 0.8.0 released on Tuesday but I've hit a new issue. I'm still investigating

partheniou@partheniou-vm-3:~/git/python-documentai-toolbox$ legacylibrarian release stage -library-version=0.16.0-alpha -library=google-cloud-documentai-toolbox
time=2026-01-22T15:21:46.640Z level=INFO msg="temporary working directory" dir=/tmp/librarian-1987239036
time=2026-01-22T15:21:46.640Z level=INFO msg="repo not specified, using current working directory as repo root" path=/usr/local/google/home/partheniou/git/python-documentai-toolbox
time=2026-01-22T15:21:46.640Z level=INFO msg="opening repository" dir=/usr/local/google/home/partheniou/git/python-documentai-toolbox
time=2026-01-22T15:21:47.007Z level=INFO msg="source not specified, skipping service config population"
time=2026-01-22T15:21:47.008Z level=INFO msg="config.yaml not found, proceeding"
time=2026-01-22T15:21:47.008Z level=INFO msg="staging a release" dir=/tmp/librarian-1987239036/output
time=2026-01-22T15:21:47.011Z level=WARN msg="bodyLine is not a header, not in a commit" bodyLine="bump version" hash=db9d5e297aa051411cf7cf58c830cb06d2cb86c7
time=2026-01-22T15:21:47.011Z level=INFO msg="library version override inputted" currentVersion=0.15.1-alpha inputVersion=0.16.0-alpha
time=2026-01-22T15:21:47.012Z level=INFO msg="=== Docker start ==============================================================="
time=2026-01-22T15:21:47.012Z level=INFO msg="/usr/bin/docker run --rm -v /usr/local/google/home/partheniou/git/python-documentai-toolbox/.librarian:/librarian -v /usr/local/google/home/partheniou/git/python-documentai-toolbox:/repo:ro -v /tmp/librarian-1987239036/output:/output --user 814163:89939 us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:b8058df4c45e9a6e07f6b4d65b458d0d059241dd34c814f151c8bf6b89211209 release-stage --librarian=/librarian --repo=/repo --output=/output"
time=2026-01-22T15:21:47.012Z level=INFO msg=--------------------------------------------------------------------------------
2026-01-22 15:21:49,306 synthtool [CRITICAL] > You are running the synthesis script directly, this will be disabled in a future release of Synthtool. Please use python3 -m synthtool instead.
2026-01-22 15:21:49,880 synthtool [DEBUG] > Using local templates at /synthtool/synthtool/gcp/templates
2026-01-22 15:21:49,888 synthtool [DEBUG] > Using local templates at /synthtool/synthtool/gcp/templates
Traceback (most recent call last):
  File "/app/./cli.py", line 1650, in handle_release_stage
    library_changes = library_release_data["changes"]
                      ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'changes'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/app/./cli.py", line 1759, in <module>
    args.func(librarian=args.librarian, repo=args.repo, output=args.output)
    ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/./cli.py", line 1676, in handle_release_stage
    raise ValueError(f"Release stage failed: {e}") from e
ValueError: Release stage failed: 'changes'
time=2026-01-22T15:21:50.299Z level=INFO msg="=== Docker end ================================================================="
time=2026-01-22T15:21:50.300Z level=ERROR msg="librarian command failed" err="exit status 1"