Skip to content

Remove stale pymupdf (AGPL-3.0) from builder app requirements#397

Merged
QuentinAmbard merged 1 commit intodatabricks-solutions:mainfrom
dayobam:remove-pymupdf-agpl
Mar 31, 2026
Merged

Remove stale pymupdf (AGPL-3.0) from builder app requirements#397
QuentinAmbard merged 1 commit intodatabricks-solutions:mainfrom
dayobam:remove-pymupdf-agpl

Conversation

@dayobam
Copy link
Copy Markdown

@dayobam dayobam commented Mar 30, 2026

Summary

  • Removes the stale pymupdf==1.27.2.2 entry from databricks-builder-app/requirements.txt
  • pymupdf (AGPL-3.0) was already replaced with PlutoPrint (MIT) in databricks-tools-core via Simplify PDF generation and remove AGPL-3.0 dependency #388, but this pinned reference was missed
  • Enterprise customers with strict license policies are flagging the repo for AGPL-3.0 during security scans, blocking adoption

Test plan

  • Verify databricks-builder-app builds and runs without pymupdf
  • Confirm no other files reference pymupdf

This pull request was AI-assisted by Isaac.

pymupdf was replaced with PlutoPrint (MIT) in databricks-tools-core
via PR databricks-solutions#388, but the pinned entry in databricks-builder-app/requirements.txt
was not removed. This stale reference causes enterprise security scans to
flag the repo for AGPL-3.0 licensing, blocking adoption.

Co-authored-by: Isaac
@QuentinAmbard QuentinAmbard merged commit 7e51873 into databricks-solutions:main Mar 31, 2026
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