Skip to content

hir-111: CHANGELOG.md + v0.1.0 baseline#26

Merged
pypesdev merged 1 commit into
mainfrom
hir-111/v0.1.0-release
May 16, 2026
Merged

hir-111: CHANGELOG.md + v0.1.0 baseline#26
pypesdev merged 1 commit into
mainfrom
hir-111/v0.1.0-release

Conversation

@jaredzwick
Copy link
Copy Markdown
Collaborator

Goal

Establish a stable versioning baseline for pypesdev/coldflow so external contributors have a target ([HIR-111], part of the OSS increments plan in HIR-105).

Changes

  1. New CHANGELOG.md at repo root in Keep a Changelog 1.1.0 format with a [0.1.0] - 2026-05-16 section listing shipped MVP features: DMARC validation, Google SMTP integration, CSV contact upload, single-step sequences, silent-reply automation, templates library.
  2. Bump package.json from 1.0.0 to 0.1.0 — the prior 1.0.0 was placeholder; v0.1.0 is the real first tagged baseline per the SemVer 0.x convention for pre-stable APIs.
  3. Templates library entry links to the merged PR hir-103: ship 10-template cold email pack #11.

After merge

  • Tag v0.1.0 on the merge commit and git push origin v0.1.0
  • Create GitHub release at releases/tag/v0.1.0 referencing the CHANGELOG section

(These follow the merge — they need to point at the main commit, not the PR branch.)

Done when

  • CHANGELOG.md merged on main
  • git tag --list v0.1.0 shows the tag locally and on origin
  • GitHub release page exists at releases/tag/v0.1.0

🤖 Generated with Claude Code

- New CHANGELOG.md in Keep-a-Changelog 1.1.0 format
- v0.1.0 section documents shipped MVP features: DMARC validation,
  Google SMTP integration, CSV contact upload, single-step sequences,
  silent-reply automation, templates library (#11)
- Bump package.json from 1.0.0 to 0.1.0 to match the tagged baseline
- v0.1.0 git tag + GitHub release follow in a separate step on main

Co-Authored-By: Paperclip <noreply@paperclip.ing>
@pypesdev pypesdev merged commit 309fc39 into main May 16, 2026
1 check passed
@pypesdev pypesdev deleted the hir-111/v0.1.0-release branch May 16, 2026 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants