briefcase 0.4.2__tar.gz → 0.4.4__tar.gz

{briefcase-0.4.2 → briefcase-0.4.4}/.github/dependabot.yml

@@ -32,3 +32,11 @@ updates:
       interval: "weekly"
       day: "sunday"
       time: "20:00"
+
+  - package-ecosystem: "pre-commit"
+    directory: "/"
+    schedule:
+      # Check for updates on Sunday, 8PM UTC
+      interval: "weekly"
+      day: "sunday"
+      time: "20:00"

briefcase-0.4.4/.github/workflows/check-pr-template.yml

@@ -0,0 +1,10 @@
+name: PR Checklist
+
+on:
+  pull_request:
+    types: [opened, edited, reopened, synchronize]
+
+jobs:
+  check-pr-template:
+    name: Check PR template
+    uses: beeware/.github/.github/workflows/pr-checklist.yml@main

{briefcase-0.4.2 → briefcase-0.4.4}/.github/workflows/ci.yml

@@ -40,10 +40,10 @@ jobs:
     continue-on-error: true
     steps:
     - name: Checkout
-      uses: actions/checkout@v6.0.2
+      uses: actions/checkout@v7.0.0
 
     - name: Set up Python
-      uses: actions/setup-python@v6.2.0
+      uses: actions/setup-python@v6.3.0
       with:
         python-version: "3.13"
 
@@ -83,12 +83,12 @@ jobs:
     timeout-minutes: 5
     steps:
       - name: Checkout
-        uses: actions/checkout@v6.0.2
+        uses: actions/checkout@v7.0.0
         with:
           fetch-depth: 1
 
       - name: Set up Python
-        uses: actions/setup-python@v6.2.0
+        uses: actions/setup-python@v6.3.0
         with:
           python-version: "3.X"
           cache: pip
@@ -132,12 +132,12 @@ jobs:
           #   experimental: true
     steps:
     - name: Checkout
-      uses: actions/checkout@v6.0.2
+      uses: actions/checkout@v7.0.0
       with:
         fetch-depth: 0
 
     - name: Set up Python
-      uses: actions/setup-python@v6.2.0
+      uses: actions/setup-python@v6.3.0
       with:
         python-version: ${{ matrix.python-version }}
         allow-prereleases: true
@@ -186,12 +186,12 @@ jobs:
     if: always() && contains('success,failure', needs.unit-tests.result)
     steps:
     - name: Checkout
-      uses: actions/checkout@v6.0.2
+      uses: actions/checkout@v7.0.0
       with:
         fetch-depth: 0
 
     - name: Setup Python
-      uses: actions/setup-python@v6.2.0
+      uses: actions/setup-python@v6.3.0
       with:
         # Use minimum version of python for coverage to avoid phantom branches
         # https://github.com/nedbat/coveragepy/issues/1572#issuecomment-1522546425

briefcase-0.4.4/.github/workflows/new-issue.yml

@@ -0,0 +1,18 @@
+name: New issue
+
+on:
+  issues:
+    types:
+      - opened
+      - reopened
+      - transferred
+
+jobs:
+  add-to-project:
+    name: Add issue to BeeWare project
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/add-to-project@v2.0.0
+        with:
+          project-url: https://github.com/orgs/beeware/projects/1
+          github-token: ${{ secrets.BRUTUS_PAT_TOKEN }}

{briefcase-0.4.2 → briefcase-0.4.4}/.github/workflows/release.yml

@@ -34,7 +34,7 @@ jobs:
           echo "VERSION=${GITHUB_REF_NAME#v}" | tee -a $GITHUB_ENV
 
       - name: Set up Python
-        uses: actions/setup-python@v6.2.0
+        uses: actions/setup-python@v6.3.0
         with:
           python-version: "3.x"
 

{briefcase-0.4.2 → briefcase-0.4.4}/.gitignore

@@ -50,8 +50,11 @@ logs/
 .specify/templates
 .specify/extensions.yml
 .specify/extensions
+.specify/feature.json
 .specify/init-options.json
 .specify/integration.json
 .specify/integrations
 .specify/workflows
 .specify/workflow.yml
+/specs/
+/docs/superpowers/

{briefcase-0.4.2 → briefcase-0.4.4}/.pre-commit-config.yaml

@@ -14,7 +14,7 @@ repos:
       - id: docformatter
         args: [--in-place, --black]
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.15.12
+    rev: v0.15.20
     hooks:
       - id: ruff-format
       - id: ruff-check

{briefcase-0.4.2 → briefcase-0.4.4}/AGENTS.md

@@ -10,6 +10,7 @@ Briefcase converts Python projects into standalone native applications for macOS
 ## Quick Reference
 
 - **Language**: Python >= 3.10 (3.10–3.14 supported)
+- **Docstrings**: Sphinx style with Markdown content
 - **Dev environment**: Python 3.13 virtualenv with `dev` dependency group
 - **License**: BSD-3-Clause
 - **Entry point**: `briefcase` via `src/briefcase/__main__.py:main()`
@@ -247,6 +248,8 @@ Types: `feature`, `bugfix`, `removal`, `doc`, `misc`.
 
 Fragment text must describe user-facing impact, not implementation details. Use `misc` for housekeeping, minor changes, or changes to features not yet in a formal release.
 
+Fragment content must use Markdown syntax.
+
 ## Documentation Style
 
 Markdown files in this project (including `AGENTS.md`, `docs/en/`, and `changes/` fragments) must **not** use hard line breaks to enforce an 80-character column limit. Each paragraph or list item must be written as a single unbroken line, regardless of its length. Let the reader's editor or renderer handle wrapping.
@@ -295,3 +298,37 @@ When writing or editing any `.md` file, do not insert newlines mid-sentence or m
       second_argument,
   )
   ```
+
+### Docstring formatting
+
+Docstrings in code must use Sphinx style with Markdown content. Use the `:param:` and `:returns:` syntax, with Markdown formatting for all docstring content:
+
+```console
+"""Construct a valid class name from a formal name.
+
+`formal_name` is used here.
+
+:param formal_name: The formal name
+:returns: The app's class name
+"""
+```
+
+## Pull request template
+
+When submitting a pull request, you must include all information requested in the pull request template:
+
+```console
+<!--- Describe your changes in detail -->
+<!--- What problem does this change solve? -->
+<!--- If this PR relates to an issue, include Refs #XXX or Fixes #XXX -->
+
+## PR Checklist:
+ <!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+ - [ ] I will abide by the BeeWare Code of Conduct
+ - [ ] I have read and have followed the **CONTRIBUTING.md** file
+ - [ ] This PR was generated or assisted using an AI tool
+ <!-- update or delete the next line to reflect your usage -->
+ Assisted-by:
+```
+
+The details of the change, and linking any related issue should come first. The PR checklist at the end must be present, and filled out appropriately; all three boxes must be checked, and `Assisted-by:` must be followed by the assisting model.

{briefcase-0.4.2 → briefcase-0.4.4}/CONTRIBUTING.md

@@ -34,4 +34,4 @@ We require that all new features have full user documentation. We have a [docume
 
 ### Pull Requests
 
-We have a [process for submitting a PR](https://briefcase.beeware.org/en/latest/how-to/contribute/how/submit-pr/) that all contributions must follow.
+We have a [process for submitting a PR](https://briefcase.beeware.org/en/latest/how-to/contribute/how/submit-pr/) that all contributions must follow. This includes the use of a [pull request template](https://github.com/beeware/.github/blob/main/.github/pull_request_template.md) that *all* pull requests must include and complete as appropriate.

{briefcase-0.4.2/src/briefcase.egg-info → briefcase-0.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: briefcase
-Version: 0.4.2
+Version: 0.4.4
 Summary: Tools to support converting a Python project into a standalone native application.
 Author-email: Russell Keith-Magee <russell@keith-magee.com>
 Maintainer-email: BeeWare Team <team@beeware.org>
@@ -99,7 +99,7 @@ Briefcase is part of the [BeeWare suite](https://beeware.org). You can talk to t
 - [Discord](https://beeware.org/bee/chat/)
 - The Briefcase [GitHub Discussions forum](https://github.com/beeware/briefcase/discussions)
 
-We foster a welcoming and respectful community as described in our [BeeWare Community Code of Conduct](https://beeware.org/community/behavior/).
+We foster a welcoming and respectful community as described in our [BeeWare Community Code of Conduct](https://beeware.org/community/code-of-conduct/).
 
 ## Contributing
 

{briefcase-0.4.2 → briefcase-0.4.4}/README.md

@@ -50,7 +50,7 @@ Briefcase is part of the [BeeWare suite](https://beeware.org). You can talk to t
 - [Discord](https://beeware.org/bee/chat/)
 - The Briefcase [GitHub Discussions forum](https://github.com/beeware/briefcase/discussions)
 
-We foster a welcoming and respectful community as described in our [BeeWare Community Code of Conduct](https://beeware.org/community/behavior/).
+We foster a welcoming and respectful community as described in our [BeeWare Community Code of Conduct](https://beeware.org/community/code-of-conduct/).
 
 ## Contributing
 

{briefcase-0.4.2 → briefcase-0.4.4}/automation/pyproject.toml

@@ -1,8 +1,8 @@
 [build-system]
 requires = [
     # keep versions in sync with ../pyproject.toml
-    "setuptools==82.0.1",
-    "setuptools_scm==10.0.5",
+    "setuptools==83.0.0",
+    "setuptools_scm==10.2.0",
     "setuptools_dynamic_dependencies @ git+https://github.com/beeware/setuptools_dynamic_dependencies",
 ]
 build-backend = "setuptools.build_meta"

{briefcase-0.4.2 → briefcase-0.4.4}/automation/src/automation/bootstraps/pyside6.py

@@ -61,6 +61,6 @@ universal_build = true
 min_os_version = "13.0"
 requires = [
     "PySide6-Addons~=6.8",
-    "std-nslog~=1.0.3",
+    "std-nslog~=2.0.0",
 ]
 """

{briefcase-0.4.2 → briefcase-0.4.4}/debugger/pyproject.toml

@@ -1,8 +1,8 @@
 [build-system]
 requires = [
     # keep versions in sync with automation/pyproject.toml and ../pyproject.toml
-    "setuptools==82.0.1",
-    "setuptools_scm==10.0.5",
+    "setuptools==83.0.0",
+    "setuptools_scm==10.2.0",
 ]
 build-backend = "setuptools.build_meta"
 
@@ -23,8 +23,8 @@ debugpy = ["debugpy>=1.8.17,<2.0.0"]
 
 [dependency-groups]
 test = [
-    "coverage[toml] == 7.13.5",
-    "pytest == 9.0.3",
+    "coverage[toml] == 7.15.0",
+    "pytest == 9.1.1",
     "pytest-xdist == 3.8.0",
 ]
 

{briefcase-0.4.2 → briefcase-0.4.4}/docs/config.yml

@@ -20,6 +20,7 @@ extra:
   min_python_version_tag: "310"  # The tag version of the minimum python version
   recent_python_version: "3.13"  # The newest Python version known to work on all platforms
   docs_python_version: "3.13"  # The version of Python required to build the documentation
+  contribution_guide_root: how-to/contribute
   social:
     - icon: fontawesome/brands/github
       link: https://github.com/beeware

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/about/releases.md

@@ -2,13 +2,60 @@
 
 <!-- towncrier release notes start -->
 
+## 0.4.4 (2026-07-08)
+
+### Bugfixes
+
+* The Toga bootstrap now enforces a dependency on `libgirepository 2.0`. This is required by changes introduced in Toga 0.5.5. ([#2919](https://github.com/beeware/briefcase/issues/2919))
+
+### Backward Incompatible Changes
+
+* The Toga app generated by Briefcase is no longer compatible with Debian 12 or Ubuntu 22.04. ([#2919](https://github.com/beeware/briefcase/issues/2919))
+
+### Misc
+
+* [#2920](https://github.com/beeware/briefcase/issues/2920), [#2921](https://github.com/beeware/briefcase/issues/2921), [#2922](https://github.com/beeware/briefcase/issues/2922), [#2923](https://github.com/beeware/briefcase/issues/2923), [#2924](https://github.com/beeware/briefcase/issues/2924), [#2925](https://github.com/beeware/briefcase/issues/2925), [#2926](https://github.com/beeware/briefcase/issues/2926)
+
+## 0.4.3 (2026-07-02)
+
+### Features
+
+* Linux system packages can now define a custom man page by setting `man_page` in `pyproject.toml`. ([#2545](https://github.com/beeware/briefcase/issues/2545))
+* macOS PKG installers can now include additional installer resources, configured with the `installer_resources` setting. ([#2561](https://github.com/beeware/briefcase/issues/2561))
+* MSI post-install and pre-uninstall scripts can now identify if they are running unattended. ([#2781](https://github.com/beeware/briefcase/issues/2781))
+* MSI installers now provide the user the ability to check disk space requirements prior to install. ([#2783](https://github.com/beeware/briefcase/issues/2783))
+* Windows MSIs with a post-install or pre-uninstall script will no longer display a console window when running in quiet mode. Script output will be captured by the installer log. ([#2789](https://github.com/beeware/briefcase/issues/2789))
+* The minimum supported Windows build number can now be specified using the `min_os_version` option. ([#2855](https://github.com/beeware/briefcase/issues/2855))
+* When a selection prompt provides a single option, it is now automatically selected as the default. ([#2856](https://github.com/beeware/briefcase/issues/2856))
+* MSI installers will now check that the app is not running or has open files before uninstalling. ([#2862](https://github.com/beeware/briefcase/issues/2862))
+* macOS PKG installers can now run a post-install script, configured with the `post_install_script` setting. ([#2865](https://github.com/beeware/briefcase/issues/2865))
+* macOS notarization state is now persisted automatically during briefcase package. If notarization is interrupted, rerunning the same package command will detect the interrupted notarization and resume it without requiring the `--resume` flag. ([#2883](https://github.com/beeware/briefcase/issues/2883))
+* The macOS notarization auto-resume workflow now allows for resuming notarization with only the distribution artefact - usually the contents of the `dist` directory. ([#2887](https://github.com/beeware/briefcase/issues/2887))
+* The macOS `package` command now accepts a `--no-wait` option that will submit an app for notarization without waiting for the notarization to complete. The submission can be finalized later by re-running `briefcase package`. ([#2888](https://github.com/beeware/briefcase/issues/2888))
+
+### Bugfixes
+
+* Briefcase now rejects project paths that contain commas or invisible left-to-right marks before project generation starts. ([#2580](https://github.com/beeware/briefcase/issues/2580))
+* Bundle identifiers with 2 parts are no longer rejected by the validation process. ([#2824](https://github.com/beeware/briefcase/issues/2824))
+* Briefcase now warns when an app's `description` is longer than 80 characters, as overly long descriptions can be truncated by some packaging formats (such as Windows MSI shortcut icons). ([#2864](https://github.com/beeware/briefcase/issues/2864))
+* Briefcase is now able to display application logs when running apps under macOS 26. If you are experiencing this problem, you will also need to either (a) upgrade `std-nslog` to 2.0.0+, or target your application at Python 3.14 (or newer). ([#2877](https://github.com/beeware/briefcase/issues/2877))
+* If a Linux Flatpak project specifies the use of a base image, Briefcase now verifies that base is installed and available. ([#2905](https://github.com/beeware/briefcase/issues/2905))
+
+### Documentation
+
+* The Windows code signing guide now describes how to generate a self-signed certificate for testing. ([#2899](https://github.com/beeware/briefcase/issues/2899))
+
+### Misc
+
+* [#2127](https://github.com/beeware/briefcase/issues/2127), [#2559](https://github.com/beeware/briefcase/issues/2559), [#2820](https://github.com/beeware/briefcase/issues/2820), [#2821](https://github.com/beeware/briefcase/issues/2821), [#2822](https://github.com/beeware/briefcase/issues/2822), [#2823](https://github.com/beeware/briefcase/issues/2823), [#2826](https://github.com/beeware/briefcase/issues/2826), [#2827](https://github.com/beeware/briefcase/issues/2827), [#2829](https://github.com/beeware/briefcase/issues/2829), [#2830](https://github.com/beeware/briefcase/issues/2830), [#2837](https://github.com/beeware/briefcase/issues/2837), [#2845](https://github.com/beeware/briefcase/issues/2845), [#2849](https://github.com/beeware/briefcase/issues/2849), [#2850](https://github.com/beeware/briefcase/issues/2850), [#2851](https://github.com/beeware/briefcase/issues/2851), [#2852](https://github.com/beeware/briefcase/issues/2852), [#2854](https://github.com/beeware/briefcase/issues/2854), [#2857](https://github.com/beeware/briefcase/issues/2857), [#2858](https://github.com/beeware/briefcase/issues/2858), [#2859](https://github.com/beeware/briefcase/issues/2859), [#2860](https://github.com/beeware/briefcase/issues/2860), [#2866](https://github.com/beeware/briefcase/issues/2866), [#2872](https://github.com/beeware/briefcase/issues/2872), [#2874](https://github.com/beeware/briefcase/issues/2874), [#2875](https://github.com/beeware/briefcase/issues/2875), [#2876](https://github.com/beeware/briefcase/issues/2876), [#2879](https://github.com/beeware/briefcase/issues/2879), [#2880](https://github.com/beeware/briefcase/issues/2880), [#2881](https://github.com/beeware/briefcase/issues/2881), [#2882](https://github.com/beeware/briefcase/issues/2882), [#2885](https://github.com/beeware/briefcase/issues/2885), [#2892](https://github.com/beeware/briefcase/issues/2892), [#2893](https://github.com/beeware/briefcase/issues/2893), [#2894](https://github.com/beeware/briefcase/issues/2894), [#2895](https://github.com/beeware/briefcase/issues/2895), [#2896](https://github.com/beeware/briefcase/issues/2896), [#2897](https://github.com/beeware/briefcase/issues/2897), [#2898](https://github.com/beeware/briefcase/issues/2898), [#2902](https://github.com/beeware/briefcase/issues/2902), [#2904](https://github.com/beeware/briefcase/issues/2904), [#2906](https://github.com/beeware/briefcase/issues/2906), [#2907](https://github.com/beeware/briefcase/issues/2907), [#2908](https://github.com/beeware/briefcase/issues/2908), [#2909](https://github.com/beeware/briefcase/issues/2909), [#2910](https://github.com/beeware/briefcase/issues/2910), [#2911](https://github.com/beeware/briefcase/issues/2911), [#2912](https://github.com/beeware/briefcase/issues/2912), [#2913](https://github.com/beeware/briefcase/issues/2913), [#2916](https://github.com/beeware/briefcase/issues/2916)
+
 ## 0.4.2 (2026-05-06)
 
 ### Features
 
 * Dynamic PEP 621 metadata in `pyproject.toml` will now be resolved by invoking the PEP 517 `[build-system]` interface. ([#474](https://github.com/beeware/briefcase/issues/474))
 * Briefcase can now build Windows apps and installers for ARM64 devices. ([#1887](https://github.com/beeware/briefcase/issues/1887))
-* License metadata in ``pyproject.toml`` is now parsed and validated using PEP 639 format (i.e., `license = "<SPDX expression>"` and `license-files = [...]`). ([#2146](https://github.com/beeware/briefcase/issues/2146))
+* License metadata in `pyproject.toml` is now parsed and validated using PEP 639 format (i.e., `license = "<SPDX expression>"` and `license-files = [...]`). ([#2146](https://github.com/beeware/briefcase/issues/2146))
 * The new project wizard now provides more detailed information about community bootstraps that are available. ([#2342](https://github.com/beeware/briefcase/issues/2342))
 * Error messages for macOS and iOS wheel compatibility now include the Python version. ([#2658](https://github.com/beeware/briefcase/issues/2658))
 * Android apps can now specify the ABIs that they target. ([#2723](https://github.com/beeware/briefcase/issues/2723))
@@ -23,7 +70,7 @@
 
 * (CVE-2026-33430) When a Windows MSI is installed for All Users, the installation folder no longer inherits the permissions of the parent folder. The fix for this issue has been backported to the templates for Briefcase v0.4.1, v0.4.0 and v0.3.26. ([#2759](https://github.com/beeware/briefcase/issues/2759))
 * Briefcase has been made more resilient to permission errors when renaming recently created directories on Windows. ([#1780](https://github.com/beeware/briefcase/issues/1780))
-* Android system image verification now uses ``sdkmanager --list_installed`` to confirm the image is fully installed, rather than only checking if the directory exists. If the image is not installed, it will be downloaded automatically. ([#1895](https://github.com/beeware/briefcase/issues/1895))
+* Android system image verification now uses `sdkmanager --list_installed` to confirm the image is fully installed, rather than only checking if the directory exists. If the image is not installed, it will be downloaded automatically. ([#1895](https://github.com/beeware/briefcase/issues/1895))
 * MSI pre/post install scripts now run with elevated privileges when installed for "All Users". ([#2722](https://github.com/beeware/briefcase/issues/2722))
 * Briefcase will now prevent the user from using an x86_64 Python interpreter on an Apple Silicon machine. ([#2736](https://github.com/beeware/briefcase/issues/2736))
 * On macOS, any wheel that doesn't contain a tag ending `-any` will now be identified as binary content that requires a merge. Previously, the `Root-Is-Purelib` wheel metadata was used to determine if a package was "pure"; this flag has proven to be unreliable under some circumstances. ([#2753](https://github.com/beeware/briefcase/issues/2753))
@@ -31,7 +78,7 @@
 
 ### Backward Incompatible Changes
 
-* Apps now require a valid PEP 639 license configuration. Apps in legacy formats — PEP 621 ``license.file``, ``license.text``, and bare free-text strings — are automatically coerced to PEP 639 format on a best-effort basis, with warnings raised about any automated conversion that has occurred. Apps with no license definition can still be built, but a placeholder license file and a `LicenseRef-UnknownLicense` license expression will be used. ([#2146](https://github.com/beeware/briefcase/issues/2146))
+* Apps now require a valid PEP 639 license configuration. Apps in legacy formats — PEP 621 `license.file`, `license.text`, and bare free-text strings — are automatically coerced to PEP 639 format on a best-effort basis, with warnings raised about any automated conversion that has occurred. Apps with no license definition can still be built, but a placeholder license file and a `LicenseRef-UnknownLicense` license expression will be used. ([#2146](https://github.com/beeware/briefcase/issues/2146))
 * New PySide6 apps now default PySide 6.10. This adds support for Python 3.14, but also enforces a minimum supported macOS version of 13.0 (Ventura). ([#2658](https://github.com/beeware/briefcase/issues/2658))
 
 ### Misc

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/about/success.md

@@ -2,7 +2,7 @@
 
 Want to see examples of Briefcase in use? Here's some:
 
-- [Travel Tips](https://github.com/freakboy3742/traveltips) is an app in the [iOS App Store](https://apps.apple.com/au/app/travel-tips/id1336372310) that was packaged for distribution using Briefcase.
+- [Travel Tips](https://github.com/freakboy3742/traveltips) is an app in the [iOS App Store](https://apps.apple.com/au/app/travel-tips/id1336372310) and [Google Play Store](https://play.google.com/store/apps/details?id=com.keith_magee.traveltips) that was packaged for distribution using Briefcase.
 - [Mu](https://codewith.mu) is a simple code editor for beginner programmers. It uses Briefcase to prepare a macOS installer.
 - [Napari](https://napari.org/) is a multidimensional image viewer for python. It uses Briefcase to prepare bundled Windows, macOS, and Linux installers.
 - [Patent Toolkit](https://patenttk.com/) is a suite of tools for patent professionals. It uses Briefcase to prepare Windows and macOS builds.

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/code-signing/windows.md

@@ -14,6 +14,30 @@ Of note, a certificate for code signing is different from a certificate for othe
 
 Additionally, it is possible to create a code signing certificate directly within Windows. However, when you create a certificate yourself, it will likely be considered "self-signed". Using such a certificate to code sign an application will not imbue it with the trust that a certificate from a Certificate Authority provides. Therefore, a self-signed certificate should not be used to code sign applications for distribution.
 
+### Creating a self-signed certificate
+
+Although a self-signed certificate is not suitable for distribution, it can be useful for testing the code signing process. The following commands, issued at a PowerShell prompt, will create a self-signed code signing certificate and install it in the `Personal` certificate store of `Current User`:
+
+```pwsh-session
+PS C:\> $cert = New-SelfSignedCertificate -Subject "My self-signed certificate" -Type CodeSigningCert -Certstorelocation Cert:\CurrentUser\My
+PS C:\> Export-Certificate -Cert $cert -FilePath my-self-signed-certificate.crt
+```
+
+Once you've done this, you can get the identity of the certificate by running:
+
+```pwsh-session
+PS C:\> $cert.Thumbprint
+```
+
+This will output the 40-character hexadecimal identity that is used by Briefcase to identify the certificate.
+
+The certificate can be converted into a password-protected PFX file using:
+
+```pwsh-session
+PS C:\> $password = ConvertTo-SecureString -String "<your password>" -Force -AsPlainText
+PS C:\> Export-PfxCertificate -Cert "Cert:\CurrentUser\My\$($cert.Thumbprint)" -FilePath my-self-signed-certificate.pfx -Password $password
+```
+
 ## Install the Certificate
 
 Once a code signing certificate is requested, Certificate Authorities may vary is how the certificate is actually delivered to you. In general, though, you'll likely receive an encrypted file containing both the certificate and its private key. Depending on the exact nature of the file format, Windows provides several commands to import certificates in to one of its certificate stores.

briefcase-0.4.4/docs/en/how-to/contribute/first-time-contributors.md

@@ -0,0 +1,3 @@
+# First-time contributors
+
+{% extends "_shared/contribute/first-time-contributors.md" %}

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/branches.md

@@ -1,3 +1,3 @@
 # Work from a feature branch, not your `main` branch
 
-{% extends "contribute/how/branches.md" %}
+{% extends "_shared/contribute/how/branches.md" %}

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/build-docs.md

@@ -1,15 +1,15 @@
 # Building documentation
 
-{% extends "contribute/how/build-docs.md" %}
+{% extends "_shared/contribute/how/build-docs.md" %}
 
 {% block front_matter %}
 
-Before you build the documentation, and have a [development environment](dev-environment.md) set up.
+Before you build the documentation, and have a [development environment](../how/dev-environment.md) set up.
 
 {% endblock %}
 
 {% block end_matter %}
 
-Once you have successfully built the docs, you are ready to [write documentation](write-docs.md).
+Once you have successfully built the docs, you are ready to [write documentation](../how/write-docs.md).
 
 {% endblock %}

briefcase-0.4.4/docs/en/how-to/contribute/how/change-note.md

@@ -0,0 +1,3 @@
+# Adding change information for release notes
+
+{% extends "_shared/contribute/how/change-note.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/how/dev-environment.md

@@ -0,0 +1,3 @@
+# Setting up a development environment
+
+{% extends "_shared/contribute/how/dev-environment.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/how/new-issue.md

@@ -0,0 +1,3 @@
+# Submitting a new issue
+
+{% extends "_shared/contribute/how/new-issue.md" %}

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/propose-feature.md

@@ -1,6 +1,6 @@
 # Proposing a new feature
 
-{% extends "contribute/how/propose-feature.md" %}
+{% extends "_shared/contribute/how/propose-feature.md" %}
 
 {% block end_matter %}
 

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/reproduce-issue.md

@@ -1,10 +1,10 @@
 # Reproducing an issue
 
-{% extends "contribute/how/reproduce-issue.md" %}
+{% extends "_shared/contribute/how/reproduce-issue.md" %}
 
 {% block front_matter %}
 
-To begin reproducing an issue, you will need a [development environment](dev-environment.md) set up.
+To begin reproducing an issue, you will need a [development environment](../how/dev-environment.md) set up.
 
 {% endblock %}
 

briefcase-0.4.4/docs/en/how-to/contribute/how/review-pr.md

@@ -0,0 +1,3 @@
+# Providing a pull request review
+
+{% extends "_shared/contribute/how/review-pr.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/how/scope-creep.md

@@ -0,0 +1,3 @@
+# Avoiding scope creep
+
+{% extends "_shared/contribute/how/scope-creep.md" %}

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/submit-pr.md

@@ -1,16 +1,16 @@
 # Submitting a pull request
 
-{% extends "contribute/how/submit-pr.md" %}
+{% extends "_shared/contribute/how/submit-pr.md" %}
 
 {% block end_matter %}
 
 {% if config.extra.website %}
 
-Your pull request may require additional content, such as a [change note](change-note.md), before it can be [reviewed](../next/pr-review.md).
+Your pull request may require additional content, such as a [change note](../how/change-note.md), before it can be [reviewed](../next/pr-review.md).
 
 {% else %}
 
-As part of submitting a pull request, you'll need to include a [change note](change-note.md) before it can be [reviewed](../next/pr-review.md).
+As part of submitting a pull request, you'll need to include a [change note](../how/change-note.md) before it can be [reviewed](../next/pr-review.md).
 
 {% endif %}
 

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/write-code.md

@@ -1,10 +1,10 @@
 # Writing, running, and testing code
 
-{% extends "contribute/how/write-code.md" %}
+{% extends "_shared/contribute/how/write-code.md" %}
 
 {% block front_matter %}
 
-To begin working on code, ensure you have a [development environment](dev-environment.md) set up, and you are [working on a branch](branches.md)
+To begin working on code, ensure you have a [development environment](../how/dev-environment.md) set up, and you are [working on a branch](../how/branches.md)
 
 {% endblock %}
 
@@ -91,6 +91,6 @@ This directs the template tests to use a branch of Briefcase for testing. This s
 
 {% block end_matter %}
 
-Once you have everything working, you can [submit a pull request](submit-pr.md) with your changes.
+Once you have everything working, you can [submit a pull request](../how/submit-pr.md) with your changes.
 
 {% endblock %}

{briefcase-0.4.2 → briefcase-0.4.4}/docs/en/how-to/contribute/how/write-docs.md

@@ -1,15 +1,15 @@
 # Writing documentation
 
-{% extends "contribute/how/write-docs.md" %}
+{% extends "_shared/contribute/how/write-docs.md" %}
 
 {% block front_matter %}
 
-Before you begin writing documentation, ensure you are able to [build the documentation](build-docs.md), and you are [working on a branch](branches.md).
+Before you begin writing documentation, ensure you are able to [build the documentation](../how/build-docs.md), and you are [working on a branch](../how/branches.md).
 
 {% endblock %}
 
 {% block end_matter %}
 
-Once you are happy with your new documentation, you can [submit a pull request](submit-pr.md) with your proposed changes.
+Once you are happy with your new documentation, you can [submit a pull request](../how/submit-pr.md) with your proposed changes.
 
 {% endblock %}

briefcase-0.4.4/docs/en/how-to/contribute/index.md

@@ -0,0 +1,3 @@
+# Contributing to {{ formal_name }}
+
+{% extends "_shared/contribute/index.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/next/pr-review.md

@@ -0,0 +1,3 @@
+# Receiving a pull request review
+
+{% extends "_shared/contribute/next/pr-review.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/next/release.md

@@ -0,0 +1,3 @@
+# The release process
+
+{% extends "_shared/contribute/next/release.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/policies/ai-policy.md

@@ -0,0 +1,3 @@
+<!-- rumdl-disable-file MD041 -->
+
+{% extends "_shared/contribute/policies/ai-policy.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/style/code-style-guide.md

@@ -0,0 +1,3 @@
+# Code style guide
+
+{% extends "_shared/contribute/style/code-style-guide.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/style/docs-style-guide.md

@@ -0,0 +1,3 @@
+# Documentation style guide
+
+{% extends "_shared/contribute/style/docs-style-guide.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/fix-issue.md

@@ -0,0 +1,3 @@
+# Fixing an issue
+
+{% extends "_shared/contribute/what/fix-issue.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/implement-feature.md

@@ -0,0 +1,3 @@
+# Implementing a new feature
+
+{% extends "_shared/contribute/what/implement-feature.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/propose-feature.md

@@ -0,0 +1,3 @@
+# Proposing a new feature
+
+{% extends "_shared/contribute/what/propose-feature.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/review-pr.md

@@ -0,0 +1,3 @@
+# Providing a pull request review
+
+{% extends "_shared/contribute/what/review-pr.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/triage.md

@@ -0,0 +1,3 @@
+# Triaging an issue
+
+{% extends "_shared/contribute/what/triage.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/use-tools.md

@@ -0,0 +1,3 @@
+# Using the tools
+
+{% extends "_shared/contribute/what/use-tools.md" %}

briefcase-0.4.4/docs/en/how-to/contribute/what/write-docs.md

@@ -0,0 +1,3 @@
+# Adding documentation
+
+{% extends "_shared/contribute/what/write-docs.md" %}