Skip to content

Conversation

@alhambrav
Copy link
Member

Ticket reference or full description of what's in the PR

Update date in support and breaking changes

@coderabbitai
Copy link

coderabbitai bot commented Sep 6, 2025

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
source/release-notes/4-4-3.rst (1)

51-53: Clarify scope of SDK 5.x requirement to avoid ambiguity

This note sits under “Studio UI” but reads as product-wide. Suggest scoping it to Studio UI & Experience Builder and pointing out other packages remain ^4.3.0 (per the compatibility table).

- CrafterCMS version 4.4.3 works with JavaScript SDK version 5.0.0 and later as mentioned in :ref:`breaking-changes-in-craftercms-4-4-3`.
-  See :ref:`compatibility-with-craftercms-version` for more information.
+ Studio UI and Experience Builder in CrafterCMS 4.4.3 require JavaScript SDK version 5.0.0 and later (see :ref:`breaking-changes-in-craftercms-4-4-3`).
+ See :ref:`compatibility-with-craftercms-version` for package-by-package details; other SDK packages remain compatible at ^4.3.0.
source/release-notes/4-x-breaking-changes.rst (1)

26-33: Good addition; tighten wording to reflect per-package compatibility

To align with the compatibility table, specify which packages require 5.x and which remain at ^4.3.0.

-CrafterCMS version 4.4.3 works with JavaScript SDK version 5.0.0 and later. See :ref:`compatibility-with-craftercms-version`
-for more information.
+CrafterCMS 4.4.3 requires JavaScript SDK 5.0.0+ for Studio UI and Experience Builder; other SDK packages remain compatible at ^4.3.0.
+See :ref:`compatibility-with-craftercms-version` for details.

Also consider updating the document header’s :last-updated: from 4.4.0 to 4.4.3 for accuracy.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 3c8d493 and dce90b2.

📒 Files selected for processing (4)
  • source/reference/api/javascript-sdk.rst (3 hunks)
  • source/release-notes/4-4-3.rst (1 hunks)
  • source/release-notes/4-x-breaking-changes.rst (1 hunks)
  • source/support.rst (1 hunks)
🔇 Additional comments (3)
source/support.rst (1)

28-28: LGTM: latest version/date updated correctly

Matches release notes for September 4, 2025. Consider verifying this date is consistent with the downloads page and any marketing pages.

source/reference/api/javascript-sdk.rst (2)

2-2: Meta updated to 4.4.3 — looks good


36-41: Compatibility section and 4.4.3 row look consistent

Anchors resolve from release notes; table values align with the narrative (EB/Studio UI ^5.0.0, others ^4.3.0).

Please double-check NPM publish ranges and that caret constraints reflect the intended minimal versions at release time.

Also applies to: 59-69

Copy link
Member

@sumerjabri sumerjabri left a comment

Choose a reason for hiding this comment

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

4.4.4

@alhambrav
Copy link
Member Author

Support page to be updated in the 4.4.4 release notes PR #2056

@sumerjabri sumerjabri merged commit 5361a6c into craftercms:master Sep 8, 2025
2 checks passed
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