Skip to content

fix(build): remove redundant force-include for default_rules.yaml - #162

Merged
vvatelot merged 1 commit into
mainfrom
fix/remove-redundant-force-include
Oct 5, 2026
Merged

vvatelot merged 1 commit into
mainfrom
fix/remove-redundant-force-include

Conversation

@vvatelot

@vvatelot vvatelot commented Oct 5, 2026

Copy link
Copy Markdown
Member

Static Badge

Summary

  • Remove [tool.hatch.build.targets.wheel.force-include] for default_rules.yaml from scraper, API, and CLI packages
  • Fix CI build failures where uv build builds a wheel from the sdist and hatchling cannot resolve the monorepo path ../../components/ecoindex/best_practices/default_rules.yaml
  • Polylith already includes non-Python brick files in wheels, so default_rules.yaml remains packaged correctly

Test plan

  • task scraper:uv:build
  • task api:uv:build
  • task cli:uv:build
  • Verify ecoindex/best_practices/default_rules.yaml is present in built wheels

Made with Cursor

The wheel force-include pointed to a monorepo path outside the sdist,
which breaks uv's two-step build (sdist then wheel). Polylith already
ships non-Python brick files, so default_rules.yaml is included without it.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown

Coverage PR 162

Branch coverage •
FileStmtsMissCoverMissing
TOTAL205758871% 
report-only-changed-files is enabled. No changed files were found in the coverage report :)

@vvatelot
vvatelot merged commit 27f4e58 into main Oct 5, 2026
6 checks passed
@vvatelot
vvatelot deleted the fix/remove-redundant-force-include branch October 5, 2026 12:24
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.

1 participant