Skip to content

docs: align README/CHANGELOG with the 5.3.0 release - #358

Merged
devondragon merged 1 commit into
mainfrom
docs/align-docs-5.3.0
Aug 15, 2026
Merged

docs: align README/CHANGELOG with the 5.3.0 release#358
devondragon merged 1 commit into
mainfrom
docs/align-docs-5.3.0

Conversation

@devondragon

Copy link
Copy Markdown
Owner

Post-release docs alignment: README install snippets and compatibility matrix to 5.3.x/5.3.0, and four factual corrections to the generated 5.3.0 changelog section (retry count 5 not 3, kebab-case fix was never a regression, removed the accessors-restored bullet that describes an intra-branch change invisible to consumers).

…ccuracies
README: dependency snippets, compatibility matrix, and version-line
references move from 5.2.x/5.2.0 to 5.3.x/5.3.0.
CHANGELOG 5.3.0 section: the registration serialization retry is 5
attempts with jittered backoff (not 3); the remember-me kebab-case fix
was not a regression (the spelling never worked in any prior release);
dropped the 'restores LoginAttemptService accessors' bullet — those
getters are unchanged relative to 5.2.0 (they were only removed and
restored within the development branch), so the note would read as an
API change that never happened.
CopilotAI lite review requested due to automatic review settings August 15, 2026 04:57
@claude

claudeBot commented Aug 15, 2026

Copy link
Copy Markdown

Review

Docs-only PR, low risk. Verified the changes:

  • Retry count fix (3 → 5, jittered backoff): confirmed against UserService.javaREGISTRATION_SERIALIZATION_ATTEMPTS = 5 with a jittered REGISTRATION_RETRY_BASE_DELAY_MS-based delay. The changelog now matches the code.
  • README version bumps (5.2.x/5.2.0 → 5.3.x/5.3.0): checked the whole file for stragglers — all references are consistently updated, no stale 5.2.x left behind. gradle.properties is at 5.3.1-SNAPSHOT, consistent with README pointing consumers at the released 5.3.0.
  • Kebab-case "not a regression" wording and dropping the "restores LoginAttemptService accessors" bullet: these are corrections to historical framing that I can't independently verify from git history in this sandbox (shallow clone, no tags), but they read as more accurate than what they replace — the old bullet described an intra-branch remove/restore that's invisible to consumers comparing 5.2.0 → 5.3.0, so dropping it avoids implying an API change that never happened from a consumer's perspective.

No code changes, no test impact. Nothing blocking — this is a clean, well-scoped documentation correction.

@devondragon
devondragon merged commit 58628b1 into mainAug 15, 2026
4 checks passed

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates post-release documentation to match the 5.3.0 (5.3.x) release line, keeping consumer-facing install guidance and the generated changelog section factually consistent with the shipped behavior.

Changes:

  • Update README compatibility matrix and installation snippets from 5.2.0/5.2.x to 5.3.0/5.3.x for Spring Boot 4.x.
  • Clarify README guidance that new feature development is on the 5.3.x line (with 3.6.x security-maintenance for Spring Boot 3.5).
  • Correct 5.3.0 changelog facts (registration retry count to 5 with jittered backoff, refine remember-me kebab/camel spelling description, remove consumer-invisible/accessor bullet).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

FileDescription
README.mdAligns compatibility/install documentation with the 5.3.x / 5.3.0 release line.
CHANGELOG.mdCorrects factual details in the 5.3.0 release notes to reflect actual shipped behavior.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for freeto 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

@devondragon