Skip to content

Conversation

@bdbch
Copy link
Member

@bdbch bdbch commented Sep 18, 2025

No description provided.

@changeset-bot
Copy link

changeset-bot bot commented Sep 18, 2025

⚠️ No Changeset found

Latest commit: c2a022e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@netlify
Copy link

netlify bot commented Sep 18, 2025

Deploy Preview for tiptap-embed ready!

Name Link
🔨 Latest commit c2a022e
🔍 Latest deploy log https://app.netlify.com/projects/tiptap-embed/deploys/68cc65169fe8db0008d9555f
😎 Deploy Preview https://deploy-preview-6984--tiptap-embed.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Sep 18, 2025

Open in StackBlitz

@tiptap/extension-character-count

npm i https://pkg.pr.new/@tiptap/extension-character-count@6984

@tiptap/extension-focus

npm i https://pkg.pr.new/@tiptap/extension-focus@6984

@tiptap/extension-dropcursor

npm i https://pkg.pr.new/@tiptap/extension-dropcursor@6984

@tiptap/extension-gapcursor

npm i https://pkg.pr.new/@tiptap/extension-gapcursor@6984

@tiptap/extension-history

npm i https://pkg.pr.new/@tiptap/extension-history@6984

@tiptap/extension-list-item

npm i https://pkg.pr.new/@tiptap/extension-list-item@6984

@tiptap/extension-list-keymap

npm i https://pkg.pr.new/@tiptap/extension-list-keymap@6984

@tiptap/extension-placeholder

npm i https://pkg.pr.new/@tiptap/extension-placeholder@6984

@tiptap/extension-table-header

npm i https://pkg.pr.new/@tiptap/extension-table-header@6984

@tiptap/extension-table-cell

npm i https://pkg.pr.new/@tiptap/extension-table-cell@6984

@tiptap/extension-table-row

npm i https://pkg.pr.new/@tiptap/extension-table-row@6984

@tiptap/extension-task-item

npm i https://pkg.pr.new/@tiptap/extension-task-item@6984

@tiptap/extension-task-list

npm i https://pkg.pr.new/@tiptap/extension-task-list@6984

@tiptap/core

npm i https://pkg.pr.new/@tiptap/core@6984

@tiptap/extension-blockquote

npm i https://pkg.pr.new/@tiptap/extension-blockquote@6984

@tiptap/extension-bubble-menu

npm i https://pkg.pr.new/@tiptap/extension-bubble-menu@6984

@tiptap/extension-bold

npm i https://pkg.pr.new/@tiptap/extension-bold@6984

@tiptap/extension-bullet-list

npm i https://pkg.pr.new/@tiptap/extension-bullet-list@6984

@tiptap/extension-code

npm i https://pkg.pr.new/@tiptap/extension-code@6984

@tiptap/extension-code-block-lowlight

npm i https://pkg.pr.new/@tiptap/extension-code-block-lowlight@6984

@tiptap/extension-code-block

npm i https://pkg.pr.new/@tiptap/extension-code-block@6984

@tiptap/extension-collaboration

npm i https://pkg.pr.new/@tiptap/extension-collaboration@6984

@tiptap/extension-collaboration-caret

npm i https://pkg.pr.new/@tiptap/extension-collaboration-caret@6984

@tiptap/extension-color

npm i https://pkg.pr.new/@tiptap/extension-color@6984

@tiptap/extension-details

npm i https://pkg.pr.new/@tiptap/extension-details@6984

@tiptap/extension-document

npm i https://pkg.pr.new/@tiptap/extension-document@6984

@tiptap/extension-drag-handle

npm i https://pkg.pr.new/@tiptap/extension-drag-handle@6984

@tiptap/extension-drag-handle-react

npm i https://pkg.pr.new/@tiptap/extension-drag-handle-react@6984

@tiptap/extension-drag-handle-vue-2

npm i https://pkg.pr.new/@tiptap/extension-drag-handle-vue-2@6984

@tiptap/extension-emoji

npm i https://pkg.pr.new/@tiptap/extension-emoji@6984

@tiptap/extension-drag-handle-vue-3

npm i https://pkg.pr.new/@tiptap/extension-drag-handle-vue-3@6984

@tiptap/extension-file-handler

npm i https://pkg.pr.new/@tiptap/extension-file-handler@6984

@tiptap/extension-floating-menu

npm i https://pkg.pr.new/@tiptap/extension-floating-menu@6984

@tiptap/extension-hard-break

npm i https://pkg.pr.new/@tiptap/extension-hard-break@6984

@tiptap/extension-font-family

npm i https://pkg.pr.new/@tiptap/extension-font-family@6984

@tiptap/extension-heading

npm i https://pkg.pr.new/@tiptap/extension-heading@6984

@tiptap/extension-highlight

npm i https://pkg.pr.new/@tiptap/extension-highlight@6984

@tiptap/extension-horizontal-rule

npm i https://pkg.pr.new/@tiptap/extension-horizontal-rule@6984

@tiptap/extension-image

npm i https://pkg.pr.new/@tiptap/extension-image@6984

@tiptap/extension-invisible-characters

npm i https://pkg.pr.new/@tiptap/extension-invisible-characters@6984

@tiptap/extension-italic

npm i https://pkg.pr.new/@tiptap/extension-italic@6984

@tiptap/extension-link

npm i https://pkg.pr.new/@tiptap/extension-link@6984

@tiptap/extension-list

npm i https://pkg.pr.new/@tiptap/extension-list@6984

@tiptap/extension-mention

npm i https://pkg.pr.new/@tiptap/extension-mention@6984

@tiptap/extension-mathematics

npm i https://pkg.pr.new/@tiptap/extension-mathematics@6984

@tiptap/extension-node-range

npm i https://pkg.pr.new/@tiptap/extension-node-range@6984

@tiptap/extension-ordered-list

npm i https://pkg.pr.new/@tiptap/extension-ordered-list@6984

@tiptap/extension-paragraph

npm i https://pkg.pr.new/@tiptap/extension-paragraph@6984

@tiptap/extension-strike

npm i https://pkg.pr.new/@tiptap/extension-strike@6984

@tiptap/extension-subscript

npm i https://pkg.pr.new/@tiptap/extension-subscript@6984

@tiptap/extension-superscript

npm i https://pkg.pr.new/@tiptap/extension-superscript@6984

@tiptap/extension-table

npm i https://pkg.pr.new/@tiptap/extension-table@6984

@tiptap/extension-table-of-contents

npm i https://pkg.pr.new/@tiptap/extension-table-of-contents@6984

@tiptap/extension-text

npm i https://pkg.pr.new/@tiptap/extension-text@6984

@tiptap/extension-text-align

npm i https://pkg.pr.new/@tiptap/extension-text-align@6984

@tiptap/extension-text-style

npm i https://pkg.pr.new/@tiptap/extension-text-style@6984

@tiptap/extension-underline

npm i https://pkg.pr.new/@tiptap/extension-underline@6984

@tiptap/extension-typography

npm i https://pkg.pr.new/@tiptap/extension-typography@6984

@tiptap/extension-unique-id

npm i https://pkg.pr.new/@tiptap/extension-unique-id@6984

@tiptap/extension-youtube

npm i https://pkg.pr.new/@tiptap/extension-youtube@6984

@tiptap/html

npm i https://pkg.pr.new/@tiptap/html@6984

@tiptap/extensions

npm i https://pkg.pr.new/@tiptap/extensions@6984

@tiptap/pm

npm i https://pkg.pr.new/@tiptap/pm@6984

@tiptap/react

npm i https://pkg.pr.new/@tiptap/react@6984

@tiptap/starter-kit

npm i https://pkg.pr.new/@tiptap/starter-kit@6984

@tiptap/suggestion

npm i https://pkg.pr.new/@tiptap/suggestion@6984

@tiptap/static-renderer

npm i https://pkg.pr.new/@tiptap/static-renderer@6984

@tiptap/vue-2

npm i https://pkg.pr.new/@tiptap/vue-2@6984

@tiptap/vue-3

npm i https://pkg.pr.new/@tiptap/vue-3@6984

commit: c2a022e

Copy link
Contributor

@alexvcasillas alexvcasillas left a comment

Choose a reason for hiding this comment

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

Thank you for addressing this!

- Check the codebase to ensure that your feature doesn't already exist.
- Check the pull requests to ensure that another person hasn't already submitted the feature or fix.

Branch targets: Pull requests should generally be opened against the `develop` branch. The only exception is a hotfix that needs to be applied immediately to `main`; in that case create the PR against `main`. After `main` has been updated (for example via a release), any commits merged into `main` must be merged back into `develop` to keep branches in sync.
Copy link
Contributor

Choose a reason for hiding this comment

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

If the change is breaking the PR would be done towards next branch right?


This repository uses Changesets to manage releases. Contributors should add a changeset for any package-level change they expect to be published; these changesets are collected and drive our release process.

Only pull requests that include a changeset will be considered for a release. If a pull request does not contain a changeset, it will not trigger a package release and therefore will not be included in the next release cycle.
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we should add this to the "Before submitting a pull request" section instead of here


### Release procedure (step-by-step)

1. Create one or more changesets for the package changes you want published. Use the `changeset` CLI or the web workflow to generate a changeset file that describes the change and the desired version bump.
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be done when creating a PR, not when doing a release, right? Maybe we should remove this step from this section?

2. Open a pull request with your changes and include the changeset file(s) in the PR. Ensure tests and linters pass before requesting review.
3. After the PR is reviewed and approved, merge it into the default branch. Only PRs that include changesets will be considered for release.
4. When changesets are merged into the default branch, the Changesets tooling will create a Release PR that aggregates proposed version bumps and compiled changelog entries for all affected packages.
5. Review the Release PR carefully. Verify that the version bumps, changelog entries, and affected packages are correct. Clean up any noisy dependency-only bumps from the changelog if appropriate.
Copy link
Contributor

Choose a reason for hiding this comment

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

Clean up any noisy dependency-only bumps from the changelog if appropriate.

This should be done when creating the release, or by editing the PR description?

@arnaugomez
Copy link
Contributor

I think the guide is missing an explanation on what difference there is between main/develop/next branches.

I have doubts whether develop is v3 or v4. If develop is still v3, then the guide should contain a step where you merge develop into main to create a new release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants