vip-governance-plugin

What's Changed

• Add a notice when the minimum PHP and WordPress version is not met by @ingeniumed in https://github.com/Automattic/vip-governance-plugin/pull/86
• Simplify the verification of the path, when a custom one is provided by @ingeniumed in https://github.com/Automattic/vip-governance-plugin/pull/89
• Add support for wildcard rules in block settings, allow programmatic generation of JSON rules, and remove blank CSS file enqueue by @ingeniumed in https://github.com/Automattic/vip-governance-plugin/pull/85

Full Changelog: https://github.com/Automattic/vip-governance-plugin/compare/1.0.9...1.0.10

• https://github.com/Automattic/vip-governance-plugin/pull/81: Restrict governance rules to apply to the post editor, and not other Gutenberg sections like the widget editor. Also adds WordPress Playground compatibility. Fixes https://github.com/Automattic/vip-governance-plugin/issues/79.

• #78: Raise the minimum WP version to 6.0 and the minimum PHP version to 8.0. In addition this also updates a lot of the dev NPM packages to their latest versions.

• https://github.com/Automattic/vip-governance-plugin/pull/71: Fixes a React style warning on disabled blocks.

Thank you to @marijnvdwerf for reporting this issue in https://github.com/Automattic/vip-governance-plugin/issues/70!

What's Changed

• https://github.com/Automattic/vip-governance-plugin/pull/67: Fix a copy-paste error in the README for vip_governance__is_block_allowed_for_editing.
• https://github.com/Automattic/vip-governance-plugin/pull/68: Fix enqueuing of resources by wrapping in plugins_url() to solve an issue in non-VIP environments.

Thank you to @marijnvdwerf for both of these fixes!

Full Changelog: https://github.com/Automattic/vip-governance-plugin/compare/1.0.5...1.0.6

• Improve the block locking for disabled blocks (#44)

• Fix the false erroring of the private directory on a VIP site not being valid for storing the governance rules (#63)

• Allow customizing the rules file that's to be used for non-vip sites, as well as for multisites (#60)
• Remove the usage of Lodash from the plugin entirely (#60)

• Update the name of the settings nav menu title from VIP Governance to VIP Block Governance (#53)

• Update the name of the plugin to WordPress VIP Block Governance (#51)
• Provide a link to this repo in the plugin location (#51)
• Reduce the development files present in the release binary (#51)

Finalize the release of the plugin, and get it out of beta status.

• Switch the analytics code to use the built in mu-plugins method.
• Improve error handling when the rules file is not found anywhere.
• Improve the README for initial use, as well as document limitations around using wp-env on non-vip sites.
• Expand list of core blocks whose nesting structure is allowed by default

• Add support for post type as a type of rule that can be used for governance purposes in the editor. This expands the flexibility that one can add to the editor, using this plugin.

• Hot fix the block recovery error that shows up when a block like core/paragraph is used under a parent in a rule's blockSettings and not at the root level. See #42 for an example of this case.

• Revamp the error handling to be faster and more informative.
• Replace the schema validation library with a bespoke version that's much faster, and more suited for this plugin.
• Updated the README with more examples for creating rule sets.
• Dropped analytics calls for non-vip/local usage.
• Added PHPDocs for better readability into the codebase.
• Dropped/Revamped core functions that were ported in order to create the inject the CSS into the editor.
• Added support for more settings from the theme.json, and documented the limitation on using duotone.

• Re-implemented block locking to be faster, and to avoid editor change warnings.
• Added more tests to ensure a larger test coverage of the codebase

• Add error analytics to the plugin.
• Combine the role specific, and default rules together for all the properties.
• Drop support for move blocks, in favor of lock blocks.
• Update the settings admin page to show the rules as different roles.
• Allow disabling child blocks independent of the parent. This functionality was removed just before the first beta went out.

Initial beta release of VIP Governance plugin.