Switch to uv

[johnewart]

This switches us from pip / setuptools / versioneer to uv / hatchling; creating a PR to ensure things run in CI as expected

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
fides-plus-nightly	Ready	Preview, Comment	Feb 11, 2026 3:25am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
fides-privacy-center	Ignored		Feb 11, 2026 3:25am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR migrates the build system from pip/setuptools/versioneer to uv/hatchling, modernizing the dependency management and build process.

Major Changes:

• Replaced setup.py, setup.cfg, and versioneer with pyproject.toml using hatchling and hatch-vcs
• Consolidated requirements.txt, dev-requirements.txt, and optional-requirements.txt into pyproject.toml dependency declarations
• Updated all GitHub Actions workflows to use uv for faster dependency installation
• Modified Dockerfile to use uv for building the application instead of pip
• Updated nox configuration to use uv as the default venv backend
• Removed 2,200+ lines of versioneer-related code

Issues Found:

• scripts/print_version.py has a package name mismatch (uses ethyca_fides but package is named ethyca-fides)
• The script uses bare except Exception which will silently hide errors
• Imports are inside try/except blocks instead of at the top of the file

Notes:

• This PR exceeds 500 line changes (343 insertions + 2578 deletions), but the vast majority is deletion of auto-generated code (versioneer.py)
• The migration appears comprehensive and consistent across all build/deployment touchpoints

Confidence Score: 3/5

• This PR has a few critical issues that need resolution before merging, particularly the package name handling in the version script
• The migration is well-structured and comprehensive, but there are syntax and logic issues in scripts/print_version.py that could cause runtime failures. The package name mismatch needs verification, and the bare except clause could hide important errors during version detection.
• Pay close attention to scripts/print_version.py which has package naming and error handling issues that need to be resolved

Important Files Changed

Filename	Overview
scripts/print_version.py	New script to print package version; has package name mismatch and bare except issues
pyproject.toml	Migration from setuptools/versioneer to hatchling/hatch-vcs with all dependencies consolidated
Dockerfile	Replaced pip-based installation with uv for faster dependency management and builds
.github/workflows/backend_checks.yml	Updated to use uv for dependency installation and removed pip caching
.github/workflows/publish_package.yaml	Switched from setup.py to uv build for package publishing

[greptile-apps]

_{5 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

package name mismatch: pyproject.toml defines the package as ethyca-fides (with hyphen) but this script uses ethyca_fides (with underscore). When installed, Python packages normalize hyphens to underscores, so this should work, but verify this is intentional.

Suggested change

	print(json.dumps({'version': version('ethyca_fides')}))
	print(json.dumps({'version': version('ethyca-fides')}))

[greptile-apps]

bare except Exception will silently hide all errors. Consider logging the error or being more specific about what exceptions to catch (e.g., PackageNotFoundError)

Suggested change

	except Exception:
	import json
	print(json.dumps({'version': 'unknown'}))
	except PackageNotFoundError:
	import json
	print(json.dumps({'version': 'unknown'}))

[greptile-apps]

imports should be at the top of the file per the custom rules, not inside try/except blocks

Suggested change

	from importlib.metadata import version
	import json
	from importlib.metadata import version, PackageNotFoundError
	import json
	try:
	print(json.dumps({'version': version('ethyca-fides')}))
	except PackageNotFoundError:
	print(json.dumps({'version': 'unknown'}))

Context Used: Rule from dashboard - Python imports should always be placed at the top of the file, not near the code that uses them. (source)

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[vercel]

Deployment failed with the following error:

Creating the Deployment Timed Out.

[adamsachs]

this broadly looks good to me, thank you! very excited to upgrade our toolchain.

we were able to verify that we could:

• successfully publish our package: https://github.com/ethyca/fides/actions/runs/21890920811/job/63196292665, https://pypi.org/project/ethyca-fides/2.78.3a2/
• successfully publish our images: https://github.com/ethyca/fides/actions/runs/21883277029, https://hub.docker.com/layers/ethyca/fides/2.78.3a0/images/sha256-ac6595ca7685397d3c4fea210e203fce17c46c61e2f8a64ad57fa0a07a105351

i also verified that referenced uv commands in the repo work well for me locally.

i'm sure there will be some quirks and things we've broken, but i think this is good enough to go, and we'll adjust/fix as those come up 👍

🚢 🚢 🚢