chore: Add changelogs to support publishing of MCP servers

[irfan-ahmed]

Description

• Added changelogs for all OCI MCP servers with information on already released versions.
• Added the current unreleased version, which will determine the next version to be published.

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• Testing in the downstream repo

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[irfan-ahmed]

@gebhardtr Can you please review this PR?

[cboffa13]

I think we should have a pre commit hook to enforce this. I dont think it has to be part of this PR but something that would be nice to have

[irfan-ahmed]

Yes. I am already working on that. I am planning to add a hook as well as a check in the lint part to check for this.

-Irfan. Confidential- Oracle Internal From: Chris Boffa ***@***.***> Date: Tuesday, November 25, 2025 at 8:22 AM To: oracle/mcp ***@***.***> Cc: Irfan Ahmed ***@***.***>, Author ***@***.***> Subject: [External] : Re: [oracle/mcp] chore: Add changelogs to support publishing of MCP servers (PR #80) @cboffa13 commented on this pull request.

________________________________ In CONTRIBUTING.md<https://urldefense.com/v3/__https://github.com/oracle/mcp/pull/80*discussion_r2560630700__;Iw!!ACWV5N9M2RV99hQ!NzCUvBccjpR-ZnjcW8B_rxYTkp4R8IhT2gJzhlMPfsoUbUajXVVYrOd7FPHqbRV0nYv_ipw0fDQbOD8E_HZ8PP41IQ$>:

@@ -42,11 +42,12 @@ can be accepted.

the issue number as part of your branch name, e.g. `1234-fixes`. 4. Ensure that any documentation is updated with the changes that are required by your change. -5. Ensure that any samples are updated if the base image has been changed. -6. Submit the pull request. *Do not leave the pull request blank*. Explain exactly +5. Ensure that any change to any of the MCP servers has a corresponding update in the CHANGELOG.md for that respective MCP server. Changes to MCP servers without corresponding changes in the CHANGELOG.MD will be rejected. I think we should have a pre commit hook to enforce this. I dont think it has to be part of this PR but something that would be nice to have — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/oracle/mcp/pull/80*pullrequestreview-3505880463__;Iw!!ACWV5N9M2RV99hQ!NzCUvBccjpR-ZnjcW8B_rxYTkp4R8IhT2gJzhlMPfsoUbUajXVVYrOd7FPHqbRV0nYv_ipw0fDQbOD8E_HZo_w02ZA$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ABTQIL4ETUDGQDGSYKXGELT36R64JAVCNFSM6AAAAACNCZ3776VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTKMBVHA4DANBWGM__;!!ACWV5N9M2RV99hQ!NzCUvBccjpR-ZnjcW8B_rxYTkp4R8IhT2gJzhlMPfsoUbUajXVVYrOd7FPHqbRV0nYv_ipw0fDQbOD8E_HYq5SVOhA$>. You are receiving this because you authored the thread.

[gebhardtr]

is this intentional?