UN-3479 [FIX] release workflow: install --all-extras to match PR gate by chandrasekharan-zipstack · Pull Request #18 · Zipstack/unstract-python-client · GitHub
Skip to content

UN-3479 [FIX] release workflow: install --all-extras to match PR gate - #18

Merged
jaseemjaskp merged 1 commit into
mainfrom
fix/release-install-all-extras
May 27, 2026
Merged

UN-3479 [FIX] release workflow: install --all-extras to match PR gate#18
jaseemjaskp merged 1 commit into
mainfrom
fix/release-install-all-extras

Conversation

@chandrasekharan-zipstack

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #17. The release-workflow dispatch on main (run 26506941508) failed at pytest collection:

tests/clone/test_cli.py:12: in <module>
    from click.testing import CliRunner
E   ModuleNotFoundError: No module named 'click'

Root cause: main.yml installs uv sync --dev but test.yml (PR gate, after #16) installs uv sync --dev --all-extras. The clone extra carries click + rich, needed for tests/clone/test_cli.py. So PR CI passed while the release dispatch failed — same code, different env.

Fix: align main.yml's install step with test.yml. Both now run uv sync --dev --all-extras.

Test plan

  • CI on this PR — lint-and-test (3.11) and lint-and-test (3.12) continue green
  • After merge: manual main.yml dispatch with minor bump → expect clean v1.3.0 release end-to-end (lint + test + build + publish + commit/tag/release all succeed)

🤖 Generated with Claude Code

test.yml installs --dev --all-extras (PR #16) so tests/clone/test_cli.py
can import click; main.yml was still on bare --dev, so the release run
failed at pytest collection while PR CI passed.

Now both workflows use identical install + lint + test commands.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@greptile-apps

greptile-apps Bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

@jaseemjaskp
jaseemjaskp merged commit 22cfd68 into main May 27, 2026
3 checks passed
@jaseemjaskp
jaseemjaskp deleted the fix/release-install-all-extras branch May 27, 2026 11:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants