chore: Prepare release v0.5.0-rc.4

[christian-kreuzberger-dtx]

Preparing the next and probably last release candidate for 0.5.0

[github-actions]

📦 Package.json Changes Detected

This PR modifies package.json. Please review the following changes carefully, and tick the following checklist boxes:

Checklist for Reviewers

• Verify that new and/or updated dependencies are necessary and from trusted sources
• Review any script changes for (security) implications
• Verify whether a new version should be released after merging the PR

Package.json Diff

diff --git a/package.json b/package.json
index 365138a..a1611d9 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@dynatrace-oss/dynatrace-mcp-server",
-  "version": "0.5.0-rc.3",
+  "version": "0.5.0-rc.4",
   "description": "Model Context Protocol (MCP) server for Dynatrace",
   "keywords": [
     "Dynatrace",

---

This comment was automatically generated by the PR Package.json Comment workflow.

[MrManny]

LGTM!

My only question is if changelog lines should consistently end their itemizations in a punct or nah. Currently it seems to be random.

Should I add a Copilot instructions file for CHANGELOG.md? 😅

[christian-kreuzberger-dtx]

LGTM!

My only question is if changelog lines should consistently end their itemizations in a punct or nah. Currently it seems to be random.

Should I add a Copilot instructions file for CHANGELOG.md? 😅

Yes, that would be great. The release process itself is also something we can let Copilot do, essentially it's

• updating version in package.json and package-lock.json (npm i --package-lock-only)
• updating CHANGELOG.md and making sure it's consistent
• Pushing those changes onto a new branch
• Creating the PR

[MrManny]

LGTM!
My only question is if changelog lines should consistently end their itemizations in a punct or nah. Currently it seems to be random.
Should I add a Copilot instructions file for CHANGELOG.md? 😅

Yes, that would be great. The release process itself is also something we can let Copilot do, essentially it's

• updating version in package.json and package-lock.json (npm i --package-lock-only)
• updating CHANGELOG.md and making sure it's consistent
• Pushing those changes onto a new branch
• Creating the PR

Neat! We pretty much trialed this via combination of a prompt file and an instruction file elsewhere, and it works pretty well. I'll open an issue in an hour and we can flesh out the scope if needed :)