chore(release): v1.1.1

[skyoo2003]

Summary

Batches the four unreleased fragments into changes/v1.1.1.md and regenerates CHANGELOG.md. Mechanical output of make changelog VERSION=v1.1.1 — no hand edits beyond a trailing newline (see below).

Related Issue

N/A — release chore.

Changes

• changes/v1.1.1.md — new, batched from the four fragments below.
• changes/unreleased/*.yaml — consumed by changie batch.
• CHANGELOG.md — regenerated by changie merge.

Contents: one Security entry (#155) and three Documentation entries (#151, #152, #154). Patch bump per SemVer: no Added or Changed fragments, and the S3 key fix is outside the guaranteed list in docs/compatibility-policy.md (wire behaviour is scoped to what tests/compatibility/ asserts, and that suite passes on 728c9fc).

One hand edit

changie batch wrote changes/v1.1.1.md without a trailing newline, so changie merge glued the next version heading onto the last entry:

...issues/154))## [v1.1.0](...) - 2026-09-06

changes/v1.1.0.md and changes/v1.0.0.md both end in 0a, and the previous CHANGELOG.md had no such run-together. Appended a newline and re-ran changie merge. Worth a follow-up so the next release does not hit it.

Test Plan

Ran the release workflow's own Verify changie release notes checks (release.yml:180-239) locally against changes/v1.1.1.md:

• exactly one version heading naming v1.1.1 — 1 of 1
• no lines outside changie's three shapes (foreign check, kinds read from .changie.yaml) — none
• every * entry ends in issues/<positive int>)) — all four
• CHANGELOG.md boundary — no run-together headings

Pre-flight per RELEASE.md, all against 728c9fc, the commit this branches from:

Check	Evidence
Generated code current	CI / codegen-drift (does the same rm -rf internal/generated && make codegen)
boto3 compatibility	Compatibility Tests
Go tests	CI / test amd64 + arm64
main green	Lint, CodeQL
Fragments carry issue numbers	grep -L 'Issue: "[0-9]' — empty
One sentence, two at most	#152 2, #151 2, #154 1, #155 1
Deprecation / compatibility review	Nothing removed; nothing on the guaranteed list changed

Note on process

RELEASE.md:116-122 says to commit and git push origin main directly. That is now blocked — ruleset 15250025 requires a pull request for main (squash only, 0 approvals). This PR is that adaptation; RELEASE.md should be updated to match.

Checklist

• Self-reviewed the code
• Added/updated tests — N/A, generated changelog only
• Lint/format passes — N/A, no Go changes
• Updated documentation — N/A
• Changie fragment — N/A, this PR is the batch