Add workflow to check Rosetta API version consistency

[jSylvestre]

Summary by CodeRabbit

• Chores
  • Added automated checks to verify that the MuleSoft Rosetta API version matches the version documented in README.md.
  • Added scheduled and manually triggered validation runs.
  • Validation results are included in the workflow summary, with failures reported when versions are missing, ambiguous, or inconsistent.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 61fd9781-0f2c-471b-9c83-3214c32aef6f

📥 Commits

Reviewing files that changed from the base of the PR and between f1218f5 and 4947328.

📒 Files selected for processing (1)

• .github/workflows/check-rosetta-api-version.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

Changes

Rosetta API version validation

Layer / File(s)	Summary
Scheduled version validation workflow .github/workflows/check-rosetta-api-version.yml	Adds scheduled and manual workflow triggers. The workflow extracts and validates the API version from the MuleSoft settings page and README.md, reports both values, and fails when either value is missing, ambiguous, or different.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 49473

This localized workflow-only change has no actionable merge-blocking risk in the supplied evidence and is merge-ready after normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant GitHubActions
  participant MuleSoftSettingsPage
  participant README
  participant JobSummary
  GitHubActions->>MuleSoftSettingsPage: Render page with headless Chrome
  MuleSoftSettingsPage-->>GitHubActions: Return API version
  GitHubActions->>README: Extract API version
  README-->>GitHubActions: Return API version
  GitHubActions->>JobSummary: Write both versions
  GitHubActions->>GitHubActions: Fail if versions are missing, ambiguous, or different

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the workflow that checks Rosetta API version consistency.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch JCS/AutoVersionCheck

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}