You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

You can read release notes on the repository releases page.

Fixed:

• Fixes launch bug from the previous release (#157).
• Fixes PWAs not using CSD when they should.

Added:

• <p>Support for bootstrapping manifest for GNU Guix (#88, thanks to @Kreyren):<br>
  Users GNU Guix can now use native/manifest.scm to provide a temporary environment with the required dependencies to build the project.</p>
• <p>Support to build and install the project using cargo-make (#89, thanks to @Kreyren):<br>
  Users can now just run makers install to automatically build and install the project.<br>
  This is now a recommended way to install the project when building from the source.</p>
• <p>Keyboard shortcut (Ctrl+Shift+N) to open a default browser (#92):<br>
  Users can now use a Ctrl+Shift+N shortcut (also available in the app menu) to open a preferred browser.<br>
  Note: When using this shortcut for the first time, you may need to select your preferred browser using the displayed dialog.</p>
• <p>Support to open link in a new tab (#94):<br>
  Added ability to force all links that should normally open in window or tab into a new tab.<br>
  This can be useful in combination with close widget change (enabled by default) for a quicker page closing.</p>
• <p>Support to enable Wayland, XInput2 and XDG Portals (#101):<br>
  Linux users can now enable Wayland, XInput2 and XDG Desktop Portals through the extension settings.</p>
• <p>Support for editing firefoxpwa.allowedDomains through settings page:<br>
  Users can now edit firefoxpwa.allowedDomains through an input on the PWA settings page.</p>
• <p>Support for setting environment variables to the runtime:<br>
  Custom environment variables for the Firefox runtime can now be passed using the variables key in the config file.</p>
• <p>Support for loading third-party UC scripts (#105):<br>
  Loader of PWAsForFirefox UserChromeJS scripts will now attempt to load chrome/user/boot.jsm in the user profile.<br>
  This can be used to load third-party UserChromeJS scripts and other modifications.</p>
• <p>Support for updating all installed PWAs (#107):<br>
  Users can now trigger an update of all installed PWAs through the extension settings.<br>
  This can also be used to automatically register all PWAs when transferring config from another device.</p>

Changed:

• Runtime and profile are now only patched when they need update (#53).
• Resume from crash functionality has been disabled by default (#86).
• Using close widget will now switch to the last tab with a scope URL if it exists (#94).
• Updated dependencies.

Fixed:

• Incorrect site grouping on Wayland (#50).
• Incorrectly overwritten preferences.
• Broken widget icons.

Important:
According to Firefox Add-on Policies, exchanging information with the native application is considered a collection of personal data and must be disclosed in a privacy policy. Unfortunately, I wasn't aware of this specific policy so I didn't prepare any privacy policy for this addon.

This release adds the privacy policy to the license agreement during the installation process to comply with Firefox Add-on Policies. The whole privacy policy is also written below:

This extension exchanges personal data (current website and manifest URLs, as well as other PWA details) with the native program when the user initiates the PWA installation. This is necessary in order to correctly obtain and parse the Web Application Manifest and install the PWA. Data are stored on the computer as long as that PWA is installed. No personal data leave the computer or are sent to third parties.

As installed PWAs are running inside a Mozilla Firefox browser, you also need to agree to the Firefox Privacy Notice.

Fixed:

• Added a privacy policy to comply with Firefox Add-on Policies.