Remove draft-release workflow; provide v3.3.3 release notes as markdown

[Copilot]

Previous session added a workflow_dispatch GitHub Actions workflow to create the draft release. This replaces that approach by removing the workflow and providing the release title and markdown body directly for manual creation via the GitHub UI.

🚀 Feature

⚙️ Optimization

🛠 Fix

• Removed .github/workflows/draft-release.yml — release notes are now provided as plain markdown to be pasted into the GitHub Releases UI directly

📖 Documentation

• Release title: v3.3.3 External Dependencies Domain + NPM Package Analysis
• Release body (covers all PRs merged after v3.3.2 — Update dependency AxonFramework/AxonFramework to v5.0.3 #531, Modularize Neo4j configuration to support profile changes #535, Update actions/setup-node action to v6.3.0 #536, Add external dependencies analysis modularized as domain #538, Analyze npm package dependencies #539, matching the section style of v3.3.1/v3.3.2):

---

🚀 Features

• Add external dependencies analysis modularized as domain: The new external-dependencies "domain" (vertical-slice) packages Cypher queries, CSV/Markdown report generation, and Python-based SVG chart generation for analyzing external dependency usage for Java and TypeScript codebases. By @JohT in Add external dependencies analysis modularized as domain #538
• Remove legacy external dependencies reports and notebooks by @JohT in Add external dependencies analysis modularized as domain #538
• Analyze npm package dependencies: Adds NPM package-level dependency analysis alongside the existing TypeScript module analysis. Initially implements longest dependency-path detection and topological sorting to provide a fast, package-level overview of the project's architecture and dependency chains. By @JohT in Analyze npm package dependencies #539
• Add TypeScript module project info to longest path visualization by @JohT in Analyze npm package dependencies #539
• Modularize Neo4j configuration and support profile changes: With useNeo4jHighMemoryProfile.sh you can now switch to the new high memory profile without redoing the whole analysis. This is helpful when you reach memory limits within your first analysis attempt and want to fix that in a simple way. By @JohT in Modularize Neo4j configuration to support profile changes #535

⚙️ Optimizations

• Add batch sizes to all transactional write operations for memory management by @JohT in Analyze npm package dependencies #539
• Improved fail-fast when running all tests by @JohT in Modularize Neo4j configuration to support profile changes #535
• Support direct and sourced test runs: You can now run each test case directly without getting an error that the script needs to be sourced. The sourced run of all tests with runTests.sh is not affected and runs as usual. By @JohT in Modularize Neo4j configuration to support profile changes #535

🛠 Fixes

• Fix wrong denominator for external module usage by @JohT in Add external dependencies analysis modularized as domain #538
• Fix misleading project scoped percentage by @JohT in Add external dependencies analysis modularized as domain #538
• Fix missing cases in external package usage by @JohT in Add external dependencies analysis modularized as domain #538
• Avoid self-loops in CHANGED_TOGETHER_WITH edges by @JohT in Analyze npm package dependencies #539
• Fix temporary directory name in maven test by @JohT in Modularize Neo4j configuration to support profile changes #535
• Fix documentation grammar issues by @JohT in Modularize Neo4j configuration to support profile changes #535

📦 Dependency Updates

• Update actions/setup-node action to v6.3.0 by @renovate[bot] in Update actions/setup-node action to v6.3.0 #536
• Update dependency AxonFramework/AxonFramework to v5.0.3 by @renovate[bot] in Update dependency AxonFramework/AxonFramework to v5.0.3 #531

Full Changelog: v3.3.2...v3.3.3

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[JohT]

The release was created via the UI with the content of the agent instead of creating a one time workflow, which wasn't the preferred solution in this case.