Skip to content

feat(deploy-candidate): Read apt dependencies from [tool.frappe-cloud] (backport #7973) - #7996

Merged
regdocs merged 1 commit into
masterfrom
mergify/bp/master/pr-7973
Nov 4, 2026
Merged

regdocs merged 1 commit into
masterfrom
mergify/bp/master/pr-7973

Conversation

@mergify

@mergify mergify Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Problem

Apps declare extra apt packages in pyproject.toml like this:

[deploy.dependencies.apt]
packages = ["libmagic1"]

This table is not valid. PEP 518 reserves all top-level tables except [tool.*] for future specifications. Strict validators such as validate-pyproject reject the file.

Change

Like the builder since frappe/agent#616, the Deploy Candidate now also reads a key in the [tool.*] namespace:

[tool.frappe-cloud]
apt-dependencies = ["libmagic1"]
  • The legacy [deploy.dependencies.apt] key still works.
  • The existing duplicate check skips a package that is already listed, so an app can list a package under both keys during migration.
  • A unit test covers both keys and the duplicate removal.

Docs: https://docs.frappe.io/wiki-app/spaces/7ncdodb8sb/change-requests/91adai4u3o


This is an automatic backport of pull request #7973 done by [Mergify](https://mergify.com).

The [deploy.dependencies.apt] table is not valid per PEP 518, which
reserves all top-level tables except [tool.*]. Strict validators reject
it. Read [tool.frappe-cloud] apt-dependencies too, like the builder does
since frappe/agent#616. The legacy key still works, and the existing
dedup lets an app list a package under both keys while it migrates.

(cherry picked from commit ad07fd2)
@mergify
mergify Bot requested a review from Aradhya-Tripathi as a code owner November 4, 2026 14:41
@regdocs
regdocs merged commit 5a9d92b into master Nov 4, 2026
7 of 8 checks passed
@regdocs
regdocs deleted the mergify/bp/master/pr-7973 branch November 4, 2026 14:41
@frappe-pr-bot

Copy link
Copy Markdown
Collaborator

🎉 This PR is included in version 0.179.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@codecov-commenter

codecov-commenter commented Nov 4, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (master@723edf0). Learn more about missing BASE report.
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##             master    #7996   +/-   ##
=========================================
  Coverage          ?   66.34%           
=========================================
  Files             ?     1142           
  Lines             ?   114470           
  Branches          ?     2171           
=========================================
  Hits              ?    75949           
  Misses            ?    38461           
  Partials          ?       60           
Flag Coverage Δ
dashboard 86.61% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants