[Release fhir 3.0.3] Prepare for next dev cycle

[ballerina-bot]

Summary

This pull request prepares the codebase for the next development cycle following the 3.0.3 release. The FHIR package version is incremented from 3.0.3 to 3.0.4 across configuration files.

Changes

• Updated package version from 3.0.3 to 3.0.4 in fhir/Ballerina.toml
• Updated package version from 3.0.3 to 3.0.4 in fhir/Dependencies.toml

All other configuration parameters and dependencies remain unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1291b74 and 375c89c.

📒 Files selected for processing (2)

• fhir/Ballerina.toml
• fhir/Dependencies.toml

---

📝 Walkthrough

Walkthrough

Version bump of the fhir package from 3.0.3 to 3.0.4 in both Ballerina.toml and Dependencies.toml configuration files. No functional changes, structural modifications, or behavioral updates.

Changes

Cohort / File(s)	Summary
Version Bump fhir/Ballerina.toml, fhir/Dependencies.toml	Package version updated from 3.0.3 to 3.0.4 in both configuration files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• [Release fhir 3.0.1] Prepare for next dev cycle #50: Same package version field updates in fhir/Ballerina.toml and fhir/Dependencies.toml.
• [Release fhir 3.0.2] Prepare for next dev cycle #54: Sequential version bump in the same configuration files (3.0.2→3.0.3, preceding this 3.0.3→3.0.4 change).

Suggested reviewers

• sameeragunarathne
• isuruh15

Poem

🐰 A minor hop from three to four,
Version numbers we adore!
No code changed, just digits bright,
The fhir package takes its flight. ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title references release of version 3.0.3, but the actual changes bump the package version to 3.0.4, creating a mismatch between the title and the actual changeset.	Update the title to reflect the correct version being prepared, such as '[Release fhir 3.0.4] Prepare for next dev cycle' to accurately represent the version bump in the changeset.
Description check	⚠️ Warning	The pull request has no description content, but the repository requires a comprehensive description template covering purpose, goals, approach, testing, security, and other critical sections.	Add a detailed pull request description following the repository template, at minimum documenting the purpose of the version bump and any relevant testing or release notes.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-fhir-v3.0.3

---

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.}