Skip to content

[Snyk] Upgrade @codemirror/state from 6.5.4 to 6.7.0#1203

Open
cld-sec wants to merge 1 commit into
masterfrom
snyk-upgrade-a011e07c19adcd6b03c2d83e060b5908
Open

[Snyk] Upgrade @codemirror/state from 6.5.4 to 6.7.0#1203
cld-sec wants to merge 1 commit into
masterfrom
snyk-upgrade-a011e07c19adcd6b03c2d83e060b5908

Conversation

@cld-sec

@cld-sec cld-sec commented Jul 15, 2026

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to upgrade @codemirror/state from 6.5.4 to 6.7.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Breaking Change Risk

Merge Risk: Low

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @codemirror/state from 6.5.4 to 6.7.0.

See this package in npm:
@codemirror/state

See this project in Snyk:
https://app.snyk.io/org/cloudinaryltd/project/96b8a37d-7953-4bdc-a10b-bd7b659552ac?utm_source=github&utm_medium=referral&page=upgrade-pr
@cld-sec

cld-sec commented Jul 15, 2026

Copy link
Copy Markdown
Author

Merge Risk: Low

This is a minor version upgrade that includes new features and bug fixes. According to the changelog, there are no breaking changes in this version range.

Key Changes:

  • 6.7.0: No changes listed for this version in the changelog.
  • 6.6.0: The exports from @codemirror/rangeset and @codemirror/text are now included in this package. This is an additive change and should not break existing code, but it allows for simplifying imports. A new feature allows adding a userEvent property directly to a transaction spec.

No mandatory migration is required.

Source: GitHub CHANGELOG.md

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

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