4.8.1

Fixed a fatal error that could happen when loading the Puc_v4_Factory class with the Composer-generated autoloader.

4.8

• Fixed a fatal error that could happen when activating two plugins or themes that use Composer autoloaders and include different versions of this library. Projects that don't use a Composer-generated autoloader were not affected.
• Fixed a compatibility warning being shown in the "View details" pop-up when the "tested up to" version was specified as major.minor (e.g. 5.2) and the site was running version major.minor.patch (e.g. 5.2.1). This complements an earlier patch where a similar warning was show on the "Updates" page.
• Fixed a potential bug where downloading a release asset from GitHub could fail if multiple plugins enabled release asset support at the same time.
• Added support for GitLab subgroups in self-hosted repositories. Props to @etlam.
• Added Catalan and Spanish translations. Props to @jorditarrida.
• Updated Japanese translation. Props to @GoodMorningCall.

4.7.1-beta2

Another test release.

4.7.1-beta

Testing a different Composer autoloading mechanism.

4.7

• Finished upgrading to BitBucket API 2.0. This should fix the "this API is no longer supported" errors experienced by some users.
• Added Solvenian translation. Props to Igor Funa.
• Minor code style changes.

4.6

• Added a puc_get_vcs_service filter that lets users add their self-hosted GitLab or BitBucket instance as a recognised service. Props to @Tofandel.
• Fixed a potentially inefficient behaviour where the update checker would check for updates every time any plugin or theme update was installed. Now it will only do that when the update is for the plugin or theme associated with that PUC instance. Props to @DavidAnderson684.
• GitLab support fix: When dealing with a self-hosted GitLab repository, the update checker will now use the protocol specified in the repository URL instead of always defaulting to HTTPS.
• Fixed a bug where, if an older version of PUC 4.x was loaded first, the more recent version's factory (Puc_v4pX_Factory) wouldn't be able to instantiate any classes.

4.5.1

Fixed a PHP notice that was triggered in PHP 7.3 when the path to the mu-plugins directory could not be resolved for some reason: "Deprecated: strpos(): Non-string needles will be interpreted as strings in the future".

4.5

• Added support for GitLab subgroups.
• Custom GitLab repository URLs can now include a port number. Props to @Spidlace.
• Added a Canadian French translation. Props to @eric-gagnon.
• Added Dutch translations. Props to @futtta.
• Fixed GitLab download URLs. Due to recent changes to the GitLab API, the old way of downloading updates no longer works. Props to @froger-me for the fix and to everyone who provided feedback/test cases in #240.
• Fixed WordPress incorrectly reporting unknown compatibility of a plugin/theme update in some cases. Props to @dangoodman.
• Fixed two PHP notices in readme-parser.php. Props to @Tofandel for one of the fixes.
• Fixed the readme parser ignoring the last readme.txt section when it's empty.
• Fixed slug conflict detection.
• Switched to generating OAuth nonces in a cryptographically secure way.

4.4

• Added a way to show a plugin icon on the "Dashboard -> Updates" page.
  Usage: Add the following entry to your JSON file:

  "icons" : {
  	"1x" : "http://example.com/assets/icon-128x128.png",
  	"2x" : "http://example.com/assets/icon-256x256.png",
  	"svg": "http://example.com/assets/icon.svg"
  } 

  See supported icon sizes and image formats.
• Added support for GitHub release assets.
  Usage: Set up the update checker instance as usual, then call the new enableReleaseAssets() method of the GitHub API class.

  $gitHubUpdateChecker->getVcsApi()->enableReleaseAssets();

  You can make PUC look for a specific asset by passing a regular expression to enableReleaseAssets(). For example, $api->enableReleaseAssets('/custom-asset/') will make PUC use the first asset where the file name contains the string "custom-asset".
• Improved error reporting when using the "check for updates" link. Previously, the check could fail with a generic message like "no updates available". Now the update checker will display the underlying API error (if available).

4.3.1

This is a hotfix to remove some debug logging code that was accidentally left in the 4.3 release.