Update changelog for version 1.18.0

[YasanPunch]

Purpose

Updated changelog

Summary

Updated the changelog to document release 1.18.0. The changelog adds a new 1.18.0 section that records the addition of observability metrics tags to the PostgreSQL client. The commit also corrects the referenced issue in the changelog entry.

Changes

• Added a new version 1.18.0 section to changelog.md
• Documented addition of observability metrics tags for the PostgreSQL client

Notes: This is a changelog-only update; no public API or exported code changes were made and review effort is low.

[coderabbitai]

Warning

Rate limit exceeded

@niveathika has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 58 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 9 minutes and 58 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 163e9474-582b-4d6e-ab24-382fce9025d6

📥 Commits

Reviewing files that changed from the base of the PR and between 887d452 and e6812b7.

📒 Files selected for processing (2)

• changelog.md
• docs/spec/spec.md

📝 Walkthrough

Walkthrough

This PR updates changelog.md by adding a new ## [1.18.0] section with an ### Added bullet documenting the application of observability metrics tags to the PostgreSQL client.

Changes

Cohort / File(s)	Summary
Changelog Update changelog.md	Added ## [1.18.0] release section and an ### Added bullet noting observability/metrics tags applied to the PostgreSQL client.

Sequence Diagram(s)

(omitted — changes are changelog-only and do not introduce new control flow)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add metrics tags to SQLDatasourceParams for Hikari Connection Pool Observability #1254: Implementation adding metrics/observability tags to SQL datasource parameters for the PostgreSQL client.

Suggested reviewers

• shafreenAnfar
• niveathika

Poem

🐇 I hopped through lines of text so neat,
A changelog added, short and sweet,
Metrics tucked into Postgre's tale,
Version 1.18 set to sail,
Hooray — observability on repeat!

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description is minimal and lacks required sections from the template such as Examples and a completed Checklist.	Expand the description to include the Examples section and a completed Checklist with checkmarks indicating which items were addressed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating the changelog for version 1.18.0.
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

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

changelog.md (1)

9-10: Consider adding a release date to 1.18.0 for changelog consistency.

Not blocking, but including - YYYY-MM-DD improves scanability and matches most released entries.

Proposed tweak

-## [1.18.0]
+## [1.18.0] - 2026-04-02

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@changelog.md` around lines 9 - 10, The changelog entry header "## [1.18.0]"
should include the release date for consistency; update the header to the format
"## [1.18.0] - YYYY-MM-DD" (replace YYYY-MM-DD with the actual release date) so
it matches other released entries and improves scanability.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@changelog.md`:
- Line 13: The changelog entry "[Add observability metrics tags to PostgreSQL
client](https://github.com/ballerina-platform/ballerina-library/issues/8572)"
references the wrong issue; update the URL portion of that markdown link to
point to the correct issue that tracks observability metrics tags (replace the
/issues/8572 suffix with the correct issue number/URL), keeping the link text
unchanged so the entry now links to the observability-related issue.

---

Nitpick comments:
In `@changelog.md`:
- Around line 9-10: The changelog entry header "## [1.18.0]" should include the
release date for consistency; update the header to the format "## [1.18.0] -
YYYY-MM-DD" (replace YYYY-MM-DD with the actual release date) so it matches
other released entries and improves scanability.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bfac8a07-8d72-482e-82c2-ce8bc1109ce4

📥 Commits

Reviewing files that changed from the base of the PR and between 8998bce and c40b0c4.

📒 Files selected for processing (1)

• changelog.md

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.62%. Comparing base (f81bd41) to head (e6812b7).
⚠️ Report is 7 commits behind head on main.

❌ Your project status has failed because the head coverage (78.62%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1256      +/-   ##
============================================
- Coverage     78.68%   78.62%   -0.07%     
+ Complexity      865      864       -1     
============================================
  Files            28       28              
  Lines          3242     3242              
  Branches        444      444              
============================================
- Hits           2551     2549       -2     
- Misses          474      475       +1     
- Partials        217      218       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.