This update fixes a few issues found in the 3.0 release of TSF.

Finally, after 8 months of preparation, experimenting, testing, and coding, TSF 3.0 is here.
This update focuses on improved social site interaction, WordPress’ API coherence, and optimizing UX.
To improve social site interaction, social site links can be added through author profile pages.
The Open Graph protocol has been updated, so will your meta output.
The canonical URL generation has been revised, and it now works mostly through WordPress’ API.
For improved UX we’ve added pixel counters, better tooltips, and admin color scheme adherence.
Oh, you can also select the primary term for each hierarchical post type.

New performance options have been added. They allow you to optimize Search and Archive query alterations.
Schema.org JSON-LD data is now cleaner when you run PHP 5.4 or later.
Custom input image URLs can now dynamically switch between HTTP and HTTPS and the dimensions are always set, regardless of input.
Multisite networks no longer initiate new database connections on every page for plugin compatibility checks.

Social images can now scale up to 4K resolution. This means (manual and automated) forced cropping no longer initiates at 1500px but at 4096px.
A new option has been added for every taxonomical post type in the Visibility tab. It allows you to prevent the annotated pages from showing up in Archives.
Structured Data output has been revisited. This includes merging of output, removal of misplaced output, and performance improvements.
When your home page is a blog, pages without an ID (404, search, date archives, etc.) had output and caching issues. These issues have been resolved.
Several security concerns have also been addressed. Although, none of them could be verified as the coding environment is already well protected.

Now, Polylang is officially supported by The SEO Framework.
The sitemap now supports plain permalinks. That means it now literally works for every website.
The robots.txt file has been enhanced, so it now informs you when the output location is incorrect.
Moreover, various bugs have been fixed, mainly concerning third party plugins.