Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #1672

Merged
merged 1 commit into from
Jan 11, 2024
Merged

Version Packages #1672

merged 1 commit into from
Jan 11, 2024

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Dec 7, 2023

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/[email protected]

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/[email protected]

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

@faustwp/[email protected]

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/[email protected]

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.

@github-actions github-actions bot requested a review from a team as a code owner December 7, 2023 11:50
@github-actions github-actions bot force-pushed the changeset-release/canary branch 4 times, most recently from 40c37d0 to 9b3872e Compare December 15, 2023 17:38
@mindctrl
Copy link
Contributor

mindctrl commented Jan 3, 2024

reminder: test blockset before merging. ref: #1656

update: tested and confirmed working

@github-actions github-actions bot force-pushed the changeset-release/canary branch 7 times, most recently from 85434e3 to 5b1f8ca Compare January 11, 2024 21:14
@blakewilson blakewilson merged commit 5bad238 into canary Jan 11, 2024
@blakewilson blakewilson deleted the changeset-release/canary branch January 11, 2024 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants