[Automated] Sync main after 1.0.0-M1-RC3 release

[wso2-integration-bot]

Automated sync of main branch after releasing version 1.0.0-M1-RC3

Summary by CodeRabbit

• Chores
  • Version bumped to 1.0.0-M1-RC3 for messagestore, websubhub-consolidator, and websubhub components
  • Project snapshot version updated to 1.0.0-M1-RC4-SNAPSHOT

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

This pull request performs a coordinated version bump across the project, updating package versions from 1.0.0-M1-RC2 to 1.0.0-M1-RC3 in multiple Ballerina manifest files and advancing the gradle.properties snapshot version from 1.0.0-M1-RC3-SNAPSHOT to 1.0.0-M1-RC4-SNAPSHOT.

Changes

Cohort / File(s)	Summary
Message Store Versioning components/messagestore/Ballerina.toml, components/messagestore/Dependencies.toml	Version bumped from 1.0.0-M1-RC2 to 1.0.0-M1-RC3
WebSubHub Consolidator Versioning components/websubhub-consolidator/Ballerina.toml, components/websubhub-consolidator/Dependencies.toml	Version bumped from 1.0.0-M1-RC2 to 1.0.0-M1-RC3
WebSubHub Versioning components/websubhub/Ballerina.toml, components/websubhub/Dependencies.toml	Version bumped from 1.0.0-M1-RC2 to 1.0.0-M1-RC3
Gradle Configuration gradle.properties	Version bumped from 1.0.0-M1-RC3-SNAPSHOT to 1.0.0-M1-RC4-SNAPSHOT

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Changes are purely version number updates in manifest files with a highly consistent, repetitive pattern across all modified files
• No logic changes, no new functionality, no structural modifications

Possibly related PRs

• [Automated] Sync main after 1.0.0-M1-RC1 release #31: Both PRs make direct, matching edits to the same manifest files (Ballerina.toml, Dependencies.toml, gradle.properties) updating package/version fields.
• [Automated] Sync main after 1.0.0-M1-RC2 release #34: Both PRs perform automated version-bump edits to the same manifest files, advancing packages from RC2→RC3 following the retrieved PR's RC1→RC2 progression.

Suggested reviewers

• anupama-pathirage
• ayeshLK

Poem

🐰 Hop, hop, versions climb so high,
RC2 to RC3, reaching for the sky,
Gradle snapshots dance and spring,
Each manifest file takes its wing,
Progress marches on with glee! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately describes the main change: synchronizing the main branch after the 1.0.0-M1-RC3 release, which matches all version bumps and gradle.properties update in the changeset.
Description check	✅ Passed	The description is minimal and lacks most required template sections (Purpose, Goals, Approach, User stories, Release note, Documentation, etc.), but it is appropriate for an automated release synchronization PR that doesn't require extensive documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-1.0.0-M1-RC3

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 03e916c and ba29f98.

📒 Files selected for processing (7)

• components/messagestore/Ballerina.toml
• components/messagestore/Dependencies.toml
• components/websubhub-consolidator/Ballerina.toml
• components/websubhub-consolidator/Dependencies.toml
• components/websubhub/Ballerina.toml
• components/websubhub/Dependencies.toml
• gradle.properties

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: ayeshLK
Repo: wso2/product-integrator-websubhub PR: 18
File: components/websubhub/Config.toml:16-26
Timestamp: 2025-11-26T14:23:02.043Z
Learning: The websubhub project (wso2/product-integrator-websubhub) has not yet been released, so configuration changes and API modifications do not need to consider backward compatibility or be treated as breaking changes.

📚 Learning: 2025-11-26T14:23:02.043Z

Learnt from: ayeshLK
Repo: wso2/product-integrator-websubhub PR: 18
File: components/websubhub/Config.toml:16-26
Timestamp: 2025-11-26T14:23:02.043Z
Learning: The websubhub project (wso2/product-integrator-websubhub) has not yet been released, so configuration changes and API modifications do not need to consider backward compatibility or be treated as breaking changes.

Applied to files:

• components/websubhub/Ballerina.toml
• components/websubhub-consolidator/Ballerina.toml
• components/websubhub/Dependencies.toml
• components/websubhub-consolidator/Dependencies.toml

🔇 Additional comments (7)

components/messagestore/Ballerina.toml (1)

4-4: Version bump looks correct.

The version has been properly updated from 1.0.0-M1-RC2 to 1.0.0-M1-RC3, consistent with the RC3 release cycle.

components/websubhub/Ballerina.toml (1)

4-4: Version bump looks correct.

The version has been properly updated from 1.0.0-M1-RC2 to 1.0.0-M1-RC3, consistent with the RC3 release cycle.

gradle.properties (1)

4-4: Version progression is correct.

The project version has been properly bumped to 1.0.0-M1-RC4-SNAPSHOT for the next development cycle following the RC3 release.

components/websubhub-consolidator/Dependencies.toml (1)

381-381: Auto-generated dependency version is correct.

The package version has been properly updated to 1.0.0-M1-RC3, matching the corresponding Ballerina.toml change.

components/websubhub-consolidator/Ballerina.toml (1)

4-4: Version bump looks correct.

The version has been properly updated from 1.0.0-M1-RC2 to 1.0.0-M1-RC3, consistent with the RC3 release cycle.

components/websubhub/Dependencies.toml (1)

393-393: Auto-generated dependency version is correct.

The package version has been properly updated to 1.0.0-M1-RC3, matching the corresponding Ballerina.toml change.

components/messagestore/Dependencies.toml (1)

360-360: Auto-generated dependency version is correct.

The package version has been properly updated to 1.0.0-M1-RC3, matching the corresponding Ballerina.toml change.

---

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 and usage tips.}