Prepare 0.6.1 release metadata

Author: dam2k

CHANGELOG.md

@@ -0,0 +1,50 @@
+# Changelog
+
+All notable changes to this project are documented here.
+
+## 0.6.1 - 2026-05-12
+
+First usable experimental pre-1.0 release.
+
+### Added
+
+- Fluent `Email` builder with sender, recipients, subject, text, HTML, custom
+  headers, attachments, data attachments, and inline data attachments.
+- MIME renderer for plain text, HTML, `multipart/alternative`,
+  `multipart/mixed`, `multipart/related`, UTF-8 subjects, UTF-8 display names,
+  UTF-8 attachment filenames, CRLF normalization, and `Bcc` envelope-only
+  handling.
+- SMTP client built directly on AMPHP sockets with TCP, implicit TLS,
+  STARTTLS, STARTTLS-if-available, `AUTH PLAIN`, `AUTH LOGIN`, envelope
+  commands, `DATA`, dot-stuffing, and `QUIT`.
+- Retry decorator for temporary SMTP failures with tested max-attempt and
+  backoff behavior.
+- Process-local rate limiting decorator with tested timing behavior.
+- `UnknownDeliveryState` for connection loss after the DATA body is sent.
+- Header and attachment safety validation for common injection vectors.
+- GitHub Actions CI for PHP 8.2, 8.3, and 8.4.
+- Manual SMTP interoperability checklist and one recorded controlled real-MTA
+  submission test.
+
+### Notes
+
+- AmpMailer is experimental and still lightly tested. Test it carefully and for
+  a long period in your own environment before relying on it in production.
+- DKIM is intentionally out of scope.
+- This package is inspired by `nette/mail`, but it is not API compatible with
+  Nette.
+- Use for spam, unsolicited email, abusive bulk email, phishing, malware,
+  harassment, unlawful mail, or provider-policy violations is strongly
+  prohibited.
+
+### Packagist Release Notes
+
+AmpMailer `0.6.1` is the first usable experimental release of a small AMPHP v3
+mailer. It includes a fluent message builder, MIME rendering, direct SMTP
+transport over AMPHP sockets, STARTTLS, SMTP AUTH PLAIN/LOGIN, retry/backoff,
+process-local rate limiting, local test coverage, PHPStan, CI, and a controlled
+real-MTA interoperability smoke check.
+
+This release is experimental and still lightly tested. Test carefully and for a
+long period in your own environment before using it in production.
+

README.md

@@ -1,5 +1,7 @@
 # AmpMailer
 
+[![CI](https://github.com/dam2k/ampmailer/actions/workflows/ci.yml/badge.svg)](https://github.com/dam2k/ampmailer/actions/workflows/ci.yml)
+
 Small AMPHP v3 mailer with MIME rendering, SMTP transport, retry, and rate limiting.
 
 ## Project Status
@@ -8,8 +10,8 @@ AmpMailer is experimental and still lightly tested. Test it carefully and for a
 long period in your own environment before relying on it in production.
 
 The current target is `0.6.1`: a small, usable pre-1.0 release with a stable
-core API, strong local test coverage, and explicit warnings about the remaining
-production validation work.
+core API, strong local test coverage, and explicit warnings about production
+validation.
 
 ## Anti-Spam Policy
 
@@ -57,10 +59,8 @@ Implemented:
 - PHPUnit tests, PHPStan analysis, Composer validation, and GitHub Actions CI
   for PHP 8.2, 8.3, and 8.4.
 
-Known gaps before tagging `0.6.1`:
-
-- Prepare release metadata: changelog, CI badge, Packagist notes, and `0.6.1`
-  tag procedure.
+Release metadata, Packagist notes, and the `0.6.1` tag procedure are documented
+in `CHANGELOG.md` and `docs/release.md`.
 
 ## Basic Usage
 

docs/release.md

@@ -0,0 +1,75 @@
+# Release Procedure
+
+This document describes the manual release flow for AmpMailer.
+
+## Pre-Release Checks
+
+Run these commands from the repository root:
+
+```bash
+php /home/dino/temp/prove/php/composer.phar validate --strict
+php /home/dino/temp/prove/php/composer.phar test
+php /home/dino/temp/prove/php/composer.phar analyse
+```
+
+Check GitHub Actions after pushing release metadata:
+
+- The `CI` workflow must be green on `main`.
+- PHP 8.2, 8.3, and 8.4 jobs must all pass.
+- Do not tag a release from a red commit.
+
+Check repository hygiene:
+
+```bash
+git status --short --branch
+rg -n "password|passwd|secret|192\\.168\\.|@tuxweb" README.md CHANGELOG.md docs src tests composer.json phpunit.xml.dist phpstan.neon.dist
+```
+
+The second command is a defensive scan. Review any match before tagging.
+
+## Packagist
+
+Package name:
+
+```text
+dam2k/ampmailer
+```
+
+Suggested description:
+
+```text
+Small AMPHP v3 mailer with MIME rendering, SMTP transport, retry, and rate limiting.
+```
+
+Use the `CHANGELOG.md` entry for the GitHub release body and Packagist release
+notes. Keep the experimental warning in the release text.
+
+## Tag 0.6.1
+
+After all checks are green:
+
+```bash
+git fetch origin
+git status --short --branch
+git tag -a 0.6.1 -m "Release 0.6.1"
+git push origin 0.6.1
+```
+
+Then verify:
+
+- The tag appears on GitHub.
+- GitHub Actions for the tag, if triggered, are green.
+- Packagist sees the new version.
+
+## Failure Handling
+
+If CI fails:
+
+1. Open the failed GitHub Actions job.
+2. Read the first real error in the log.
+3. Reproduce the same command locally.
+4. Fix the code or documentation.
+5. Run all pre-release checks again.
+6. Commit and push the fix.
+7. Tag only after the latest commit is green.
+