Skip to content

docs: fix release date and label inconsistencies - #13

Merged
btcneves merged 1 commit into
mainfrom
fix/docs-version-date-consistency
May 21, 2026
Merged

btcneves merged 1 commit into
mainfrom
fix/docs-version-date-consistency

Conversation

@btcneves

@btcneves btcneves commented May 21, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • docs/release-notes-v1.2.0.md — corrects release date from 2026-05-20 to 2026-05-21, aligning with the CHANGELOG.md entry and the actual commit timestamp (c832f34).
  • docs/release-notes-v0.7.0.md — normalizes the release label from **Released:** to **Release date:**, matching the format used in every other release notes file in the repository.

Test plan

  • Verify docs/release-notes-v1.2.0.md line 3 reads **Release date:** 2026-05-21
  • Verify docs/release-notes-v0.7.0.md line 3 reads **Release date:** 2026-05-20
  • Confirm no other release notes file uses **Released:** as the label

- release-notes-v1.2.0: correct release date from 2026-05-20 to 2026-05-21
  (aligns with CHANGELOG.md entry and actual commit timestamp)
- release-notes-v0.7.0: normalize label from "Released:" to "Release date:"
  to match the format used across all other release notes files
@btcneves
btcneves merged commit 56f8423 into main May 21, 2026
1 check passed
@btcneves
btcneves deleted the fix/docs-version-date-consistency branch May 21, 2026 13:11
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.

1 participant