Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.

Releases

@faustwp/cli@2.0.0

Major Changes

• c163fa5: BREAKING: Removed telemetry CLI commands for faust telemetry enable/disable/status for managing and viewing telemetry opt-in status. Telemetry functionality has been moved to the Faust WordPress plugin. Sites that previously opted in from CLI will no longer send telemetry data unless someone opts in from the WordPress side.

Patch Changes

• c163fa5: Adds block_editor_utils and experimental_app_router to telemetry events.

@faustwp/block-editor-utils@0.1.0

Minor Changes

• 8dcda28: Add support for RichText control fields.

  Add a source and selector in your block attributes string field:

  ...
  "attributes": {
  		"richText": {
  			"type": "string",
  			"source": "html",
  			"selector": ".rich-text",
  			"default": "Hello World"
  		}
  	}

  Then in your component definition make sure the selector specifier matches the component you want to render as rich text:

  <div
    style={styles}
    className="rich-text"
    dangerouslySetInnerHTML={{ __html: attributes.richText }}
  />

  Once the blocks are synced you will be able to use it as a RichText field.

Patch Changes

• 66c1e24: Publish Readme to NPM

@faustwp/core@2.0.0

Minor Changes

• c79c8c2: Added the ability to provide multiple queries to a given Faust Template:

  import {GET_POST, GET_LAYOUT} from './queries.js'
  
  export default function Component(props) {
  }
  
  Component.queries = [
    {
      query: GET_LAYOUT
    },
    {
      query: GET_POST,
      variables: (seedNode, ctx) {
        return {
          id: seedNode.databaseId,
          asPreview: ctx?.asPreview
        }
      }
    }
  ]

  Note: Your Faust template can use either Component.queries or Component.query, but not both.

@faustwp/wordpress-plugin@1.2.0

Minor Changes

• 5f78b15: Requests to robots.txt on the WordPress site are now accessible and are no longer redirected to the front-end site.
• c163fa5: Added support for anonymous opt-in telemetry. Previously this functionality was in the Faust CLI package, but has been moved to the WordPress plugin instead. All telemetry collection is optional and anonymous, and it is disabled by default. If you were previously opted in from Faust CLI, once you update the Faust CLI packages your site will no longer send telemetry data unless you opt in again from the WordPress plugin.

Patch Changes

• 205fb09: Improved plugin's process for handling blockset file uploads by leveraging WordPress' native unzip_file function.
• 41a6d9c: Fixed issue where term URIs were rewritten from relative to absolute during GraphQL requests when they should not have been. This was causing nodeByUri queries for terms to fail.
• e725bda: Adds phpstan to CI/CD workflow. Runs as part of the lint step.

[mindctrl]

reminder: test blockset before merging. ref: #1656

update: tested and confirmed working