Add CHANGELOG.md and automated release tag workflow for v0.1.0

[Copilot]

Release 0.1.0 - Complete ✅

• Verify package.json version is 0.1.0
• Create CHANGELOG.md with comprehensive release notes
• Verify all tests pass (95 tests passing)
• Verify build succeeds (TypeScript compilation successful)
• Review release workflow configuration (.github/workflows/release.yml)
• Run code review (no issues found)
• Run security scan (no vulnerabilities)
• Simplify CHANGELOG.md per feedback
• Add workflow to create release tag from package.json version
• Improve workflow error handling

Summary

This PR prepares the repository for the v0.1.0 initial release of Odette. All necessary changes have been completed:

Changes Made

• ✅ Added simplified CHANGELOG.md following Keep a Changelog format
• ✅ Version 0.1.0 already set in package.json
• ✅ All tests passing (95/95)
• ✅ Build verified and working
• ✅ Added .github/workflows/create-release-tag.yml workflow with robust error handling

New Workflow: Create Release Tag

A new GitHub Actions workflow has been added that automates the tag creation process. After this PR is merged to main, the release can be triggered:

Option 1: Use the automated workflow (recommended)

1. Go to Actions → "Create Release Tag" workflow
2. Click "Run workflow"
3. The workflow will automatically:
   • Read the version from package.json (currently 0.1.0)
   • Validate package.json exists and has a version field
   • Check if tag already exists
   • Create tag v0.1.0 if it doesn't exist
   • Push the tag to GitHub
   • Automatically trigger the release workflow

Option 2: Manual tag creation

git checkout main
git pull
git tag -a v0.1.0 -m "Release v0.1.0"
git push origin v0.1.0

Release Workflow

Once the tag is pushed (via either method), the GitHub Actions release workflow will automatically:

1. Run all tests
2. Build the TypeScript application
3. Create a GitHub release with auto-generated release notes
4. Build and push Docker images to ghcr.io/cdanis/odette with tags: 0.1.0, 0.1, and latest
5. Create and attach a release tarball artifact

Original prompt

Release 0.1.0

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[cdanis]

You don't need any more content after this @copilot

[Copilot]

Simplified to just the initial release line. Fixed in 3cac642.

[cdanis]

@copilot can you create the tag yourself somehow ?

[Copilot]

@copilot can you create the tag yourself somehow ?

I can create the tag locally (git tag -a v0.1.0 -m "Release v0.1.0"), but I don't have the authentication or permissions to push it to GitHub. The git push fails with authentication errors, and I don't have access to the GitHub API to create releases.

You'll need to push the tag manually after merging this PR:

git checkout main
git pull
git tag -a v0.1.0 -m "Release v0.1.0"
git push origin v0.1.0

This will trigger the release workflow in .github/workflows/release.yml.

[cdanis]

@copilot can you implement a GitHub action to create a tag from the version in packages.json ? And then invoke it

[Copilot]

@copilot can you implement a GitHub action to create a tag from the version in packages.json ? And then invoke it

Created the workflow in .github/workflows/create-release-tag.yml (commit 7a80e31).

The workflow reads the version from package.json and creates/pushes a tag automatically. However, I cannot trigger it because:

1. workflow_dispatch only works on workflows in the default branch (main)
2. I don't have GitHub API access to trigger workflows

After this PR is merged to main, you can trigger it:

• Go to Actions → "Create Release Tag" → "Run workflow"
• Or via CLI: gh workflow run create-release-tag.yml

This will create tag v0.1.0 and trigger the release workflow automatically.