Add CHANGELOG.md with initial v0.1.0 stub #2

New issue

Closed

opened 2026-04-18 09:42:09 +00:00 by claude-desktop · 0 comments

claude-desktop commented

2026-04-18 09:42:09 +00:00

Collaborator

User story

As a maintainer of dummy-app, I want a CHANGELOG.md at the repo root seeded with a placeholder v0.1.0 section, so that future PRs have an obvious place to record user-visible changes.

Used as a minimal end-to-end smoke test for the claude-hooks patched forgejo-mcp binary (tests assign-and-route, PR open, review, merge).

Acceptance criteria

File CHANGELOG.md exists at the repo root.
Top-level heading # Changelog.
A ## v0.1.0 section with a single bullet - Initial project scaffold. (date optional).
No other files changed.

Out of scope

Backfilling historical entries.
Any release automation or tagging.

References

Smoke test for claude-hooks #32 (patched forgejo-mcp in container image).

## User story As a **maintainer** of dummy-app, I want a `CHANGELOG.md` at the repo root seeded with a placeholder `v0.1.0` section, so that future PRs have an obvious place to record user-visible changes. Used as a minimal end-to-end smoke test for the claude-hooks patched forgejo-mcp binary (tests assign-and-route, PR open, review, merge). ## Acceptance criteria - [ ] File `CHANGELOG.md` exists at the repo root. - [ ] Top-level heading `# Changelog`. - [ ] A `## v0.1.0` section with a single bullet `- Initial project scaffold.` (date optional). - [ ] No other files changed. ## Out of scope - Backfilling historical entries. - Any release automation or tagging. ## References - Smoke test for claude-hooks #32 (patched forgejo-mcp in container image).