Skip to content

Issue #1071: chore: remove the unused setup-poetry composite action - #1306

Merged
bjagg merged 1 commit into
LIF-Initiative:mainfrom
bjagg:chore/issue-1071-retire-setup-poetry
Sep 24, 2026
Merged

bjagg merged 1 commit into
LIF-Initiative:mainfrom
bjagg:chore/issue-1071-retire-setup-poetry

Conversation

@bjagg

@bjagg bjagg commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor
Description of Change

Problem. #1071 asks us to standardize on uv and retire Poetry from the build path. The only Poetry left in the build path is the setup-poetry composite action.

Solution. Delete .github/actions/setup-poetry/action.yml. No workflow calls it. Every service builds with uv (#1067, #1068), and a search for setup-poetry under .github/ finds only the action's own file. After this, uv is the single Python build toolchain.

Side effects. None expected. The action also ran pip install earthmover, but since nothing calls the action, that install never runs today.

Not changed, deliberately:

  • .gitignore / orchestrators/dagster/lif-orchestrator/.gitignore: the # poetry lines are stock Python .gitignore template comments, not tooling.
  • Other "poetry" matches are the English word in schema and sample data (Evidence.genre descriptions).
  • docs/operations/proposals/cf-ci-improvements.md item 6 still describes the action. That document is an outside review recording what it found, so it is left as a record rather than edited.

How to test. git grep -n "setup-poetry" -- .github returns nothing on this branch, and the PR-time CI plus every deploy workflow run unchanged because none of them referenced the action.

Related Issues

Closes #1071
Refs #1074

Type of Change
  • Infrastructure/deployment change
  • Code refactoring
Project Area(s) Affected
  • .github/actions/ (CI composite actions)

Checklist
  • commit message follows commit guidelines (see commitlint.config.mjs)
  • pre-commit hooks have been run successfully: not run locally (hooks are not installed in the authoring clone). The change only deletes a file; the commit message is checked by the CI commitlint job, and ruff/ty/pytest by pr-ci.
Testing
  • Manual testing performed: verified no remaining setup-poetry references in .github/

🤖 Generated with Claude Code

…osite action

The last Poetry in the build path was .github/actions/setup-poetry, and no
workflow references it: every service builds with uv (LIF-Initiative#1067, LIF-Initiative#1068), and a
repo-wide search for "setup-poetry" under .github/ finds only the action's own
file. Deleting it leaves uv as the single Python build toolchain.

The action also pip-installed earthmover. Nothing runs that install today,
since the action is never called, so removing it changes no build.

Remaining "poetry" matches in the repo are stock .gitignore template comments
and the English word in schema/sample data, none of them build tooling.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bjagg
bjagg merged commit d8bc7cc into LIF-Initiative:main Sep 24, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

CF/CI: standardize Python build tooling on uv (retire poetry from the build path)

1 participant