Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package Automation with Briefcase in CI #1562

Merged
merged 3 commits into from
Dec 5, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ jobs:
package:
name: Python package
uses: beeware/.github/.github/workflows/python-package-create.yml@main
with:
tox-factors: -with-automation

unit-tests:
name: Unit tests
Expand Down
1 change: 1 addition & 0 deletions changes/1562.misc.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
CI will now create a wheel for Automation as well as Briefcase to support running the packaged app in CI testing.
2 changes: 1 addition & 1 deletion docs/reference/configuration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -503,7 +503,7 @@ PEP621 compatibility

Many of the keys that exist in Briefcase's configuration have analogous settings
in `PEP621 project metadata
<https://packaging.python.org/en/latest/specifications/declaring-project-metadata>`__.
<https://packaging.python.org/en/latest/specifications/pyproject-toml/>`__.
If your ``pyproject.toml`` defines a ``[project]`` section, Briefcase will honor
those settings as a top level definition. Any ``[tool.briefcase]`` definitions
will override those in the ``[project]`` section.
Expand Down