Skip to content

Latest commit

 

History

History
128 lines (78 loc) · 6.66 KB

CHANGELOG.md

File metadata and controls

128 lines (78 loc) · 6.66 KB

Changelog

2.0.1

Patch Changes

  • #1122 af94d16 Thanks @dotboris! - Set minimum version of Chrome to 121. This is the first version of Chrome that ignores the background.scripts property in manifest.json. We need this property to be ignored because we distribute this extension in Firefox which requires this key.

  • #1122 af94d16 Thanks @dotboris! - Set minimum version of Firefox to 112. This is the first version version of Firefox to support both Manifest v3 and the background.type property.

  • #1118 4d6325b Thanks @renovate! - Give icons accessible labels based their titles

2.0.0

Major Changes

  • #1004 54aad0d Thanks @dotboris! - Migrate to Manifest v3

    This is considered a breaking change because a change in the web extension permission model might require some users to accept new permissions. To resolve this, simply open the Prod Guard popup. If you have new permissions to accept, you'll see a yellow warning guiding you through the process.

    The permission in question is "Access data for all websites". We use this permission to inject the warnings that you have configured. Note that this is not a new permission. In Manifest v2, this permission was granted to use automatically when you installed Prod Guard. In Manifest v3, browsers may no longer grant this permission implicitly. From our testing, we've seen this behavior in Firefox.

Patch Changes

  • #1092 5bf3f7b Thanks @dotboris! - Change the font family to Roboto and the font size to 16px. Previously the font was not set and would therefore default to whatever the browser had. This ensures a more consistent look and feel across browsers and platforms.

1.5.1

Patch Changes

  • #1036 3ad8c34 Thanks @dotboris! - Fix issue where long URL patterns would overflow off the popup. This lead to the icons next to the pattern being hidden.

1.5.0

Minor Changes

  • #1016 435bdc7 Thanks @dotboris! - Warning can now be toggled on & off. Warnings that are toggled off don't get injected into pages.

1.4.0

Minor Changes

  • #1008 bbbe2ad Thanks @dotboris! - Allow users to import data into Prod Guard. This can be done through the new settings menu. Settings are accessible in the popup by clicking the cog icon on the top right.

  • #999 fcfde78 Thanks @dotboris! - Allow users to export all of Prod Guard's data. This can be done through the new settings menu. Settings are accessible in the popup by clicking the cog icon on the top right.

Patch Changes

  • #988 cd4a8c0 Thanks @dotboris! - Fix bug where internal state migration process would replace already configured settings for warnings with their default values.

  • #991 16566e9 Thanks @renovate! - Update all non-major dependencies

  • #998 3d1f781 Thanks @dotboris! - Fix a bug where the color fields of a warning could be set to a blank value. The color fields are now all required when creating / editing a warning.

1.3.1

Fixed

  • Fix bug where banners would stay invisible or partially visible when mouse leaves the window. #774

Changed

  • Rename the master branch to main. This should have 0 impact on end users but it's worth mentioning.

1.3.0

Added

  • Top and bottom banners now automatically hide themselves when the mouse gets close. This allows you to see what's underneath a banner and to click or interact with the parts of the page that would be under the banner.

Changed

  • Change internal IDs from temporary integers to permanent UUIDs. This is an internal change that should not have any effect on users. This change is in preparation for adding an import/export feature.

1.2.0

Added

  • It is now possible to change the text for the "Top Banner" and "Bottom Banner" style warnings.
  • It is now possible to change the colors of all warnings.

Changed

  • Migrate the whole build process to Webpack 5. This should have no impact on end users but it's worth mentioning.
  • Migrate tests to Jest. This should have no impact on end users but it's worth mentioning.
  • Migrate codebase from Vue.js to React. This should have no impact on end users but it's worth mentioning.

1.1.1

Fixed

  • Fixed major bug where loading, adding, removing, changing warnings did not work at all but only on the published version of the extension. It works in dev but it falls flat when it's published for real.

1.1.0

Added

  • Added support for Chrome & Chromium

1.0.0

Added

  • Ability to add warning to websites based regular expressions.
  • Top Banner style warning.
  • Bottom Banner style warning.
  • Border style warning.
  • Interface for managing warnings.