Feature to add anchor attribute to core/paragraph block

[jan-clockworkwp]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.
  • Note: Last referenced version of @faustjs/blocks package on canary branch by the changeset package was 4.0.1 but in the code was version 5.0.0, so that is the reason why my changeset entry is marked as major change.

Description

As mentioned in the following feature request, an anchor attribute was added in the @faustjs/blocks package and the CoreParagraph block.

Related Issue(s):

[feat] Add anchor attribute to core/paragraph block #1954

Testing

1. In the WordPress application add native Gutenberg feature HTML Anchor to any paragraph block.
2. Check front end Faust application and see if the paragraph is properly rendered with id tag of HTML anchor value.
3. Additionally, run npm run test from the @faustjs/blocks package root to run all blocks code tests

Note: This feature is needed only for the templates where the content is being rendered with the WordPressBlocksViewer component.

Screenshots

Documentation Changes

Dependant PRs

[headless-platform-by-wp-engine]

Currently, we do not support the creation of preview deployments based on changes coming from forked repositories.
Learn more about preview environments in our documentation.

[changeset-bot]

🦋 Changeset detected

Latest commit: 528f11e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@faustwp/blocks	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[theodesp]

thanks @jan-clockworkwp

[theodesp]

This should be a patch version instead, We are not breaking anything.

[jan-clockworkwp]

@theodesp btw there is a note in the Tasks section related to it, and I was not sure how to correct semver and code mismatch properly.

Note: Last referenced version of @faustjs/blocks package on canary branch by the changeset package was 4.0.1 but in the code was version 5.0.0, so that is the reason why my changeset entry is marked as major change.

[theodesp]

This should be a patch version instead. We are not breaking anything.

[jan-clockworkwp]

Hi @theodesp, I was just trying to follow semver that, if I understand correctly, patch bumps are meant for backwards-compatible bug fixes, and minor bumps are for backwards-compatible new feature releases. I naturally considered this a new feature as it was adding functionality, but it could have been considered a fix as well. Do you want me to change it to version 5.0.1 instead?