Skip to content

Conversation

@jffortier
Copy link
Contributor

@jffortier jffortier commented Dec 11, 2024

Background

This PR brings content from unstable that was missed in the previous 2024-10-2 release AND brings content update that came from our Request to Release review.

Checklist

  • I have 🎩'd these changes
  • I have updated relevant documentation

@jffortier jffortier force-pushed the jffortier/2024-10-content-updates branch from e1c0046 to 99827ce Compare December 11, 2024 21:34
@jffortier jffortier marked this pull request as ready for review December 11, 2024 21:35
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jffortier since this is just a doc change, you don't need to add a change log unless you do want to publish a new version of the package. If you exclude this, it won't add a new patch version.

@github-actions
Copy link
Contributor

We detected some changes in packages/*/package.json or packages/*/src, and there are no updates in the .changeset directory. If the changes are user-facing and should cause a version bump, run yarn changeset to track your changes and include them in the next release CHANGELOG. If you are making simple updates to repo configuration, examples, or documentation, you do not need to add a changeset.

@jffortier jffortier merged commit bf7a873 into 2024-10 Dec 12, 2024
6 checks passed
@jffortier jffortier deleted the jffortier/2024-10-content-updates branch December 12, 2024 15:20
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.

3 participants