v0.3.2

Features

• Added pytest coverage to CI/CD process. (#417)
• Application metadata now contains a Briefcase-Version indicator. (#425)
• The device list returned by briefcase run android now uses the Android device model name and unique ID e.g. a Pixel 3a shows up as Pixel 3a (adbDeviceId). (#433)
• Android apps are now packaged in Android App Bundle format. This allows the Play Store to dynmically build the smallest APK appropriate to a device installing an app. (#438)
• PursuedPyBear is now included in the new project wizard. (#440)

Bugfixes

• iOS builds will now warn if the Xcode command line tools are the active development environment. (#397)
• Linux Docker builds no longer use interactive mode, allowing builds to run on CI (or other TTY-less devices). (#439)

Improved Documentation

• Documented the process of signing Android apps & publishing them to the Google Play store. (#342)

Misc

• #428

Release v0.3.1

Features

• The Linux AppImage backend has been modified to use Docker. This ensures that
  the AppImage is always built in an environment that is compatible with the
  support package. It also enables Linux AppImages to be built on macOS and
  Windows. "Native" builds (i.e., builds that don't use Docker) can be invoked
  using the --no-docker argument. (#344)
• A PYTHONPATH property has been added to AppConfig that describes the
  sys.path changes needed to run the app. (#401)
• Ad-hoc code signing is now possible on macOS with briefcase package --adhoc-sign. (#409)
• Android apps can now use use - in their bundle name; we now convert -
  to _ in the resulting Android package identifier and Java package name. (#415)
• Mobile applications now support setting the background color of the splash
  screen, and setting a build identifier. (#422)
• Android now has a package command that produces the release APK. After
  manually signing this APK, it can be published to the Google Play Store. (#423)

Bugfixes

• Some stray punctuation in the Android device helper output has been removed. (#396)
• An explicit version check for Docker is now performed. (#402)
• The Linux build process ensures the Docker user matches the UID/GID of the host
  user. (#403)
• Briefcase now ensures that the Python installation ecosystem tools (pip,
  setuptools, and wheel), are all present and up to date. (#421)

Improved Documentation

• Documented that Windows MSI builds produce per-user installable MSI installers,
  while still supporting per-maching installs via the CLI. (#382)
• CONTRIBUTING.md has been updated to link to Briefcase-specific
  documentation. (#404)
• Removed references to the build-system table in pyproject.toml. (#410)

Release v0.3.0

This is a major backwards incompatible release. It is a complete, ground up rewrite of Briefcase, converting it into a PEP518 build tool instead of a setuptools extension.

It also dramatically improves support on all platforms, and contains a comprehensive test suite.

Release v0.3.0.dev8

• Allowed for different device formats returned by simctl for iOS.
• Corrected path handling for Windows when there are multiple source paths.
• Fixed the stub publish command for macOS.
• Honor Content-Disposition headers when downloading resources.

Release v0.3.0.dev7

• Improves error handling when git is not installed
• Sets a maximum version on Jinja2 to preserve Python 3.5 compatibility.

Release v0.3.0.dev6

• Addressed a packaging problem with GitPython
• Various documentation improvements.

Release v0.3.0.dev5

• Removes the dependency on boto by using the briefcase-support.org proxy for providing support packages.

Release v0.3.0.dev4

Bugfix release; corrects error seen during packaging of macOS DMGs

Release v0.3.0.dev3

• Normalized the naming of names (so name becomes app_name)
• Ensure that the full app ID is included in app metadata.

Release v0.3.0.dev2

• Splits the "build" command into "build" and "package".
• Adds code signing for macOS apps
• Corrected some minor capitalization issues in wizard prompts
• Corrected some problems associated with short source paths.