Skip to content

v3.1 (5/N): finalize CHANGELOG under [3.1.0]#10

Merged
jlc488 merged 2 commits into
mainfrom
v3.1.0/release-finalize
May 23, 2026
Merged

v3.1 (5/N): finalize CHANGELOG under [3.1.0]#10
jlc488 merged 2 commits into
mainfrom
v3.1.0/release-finalize

Conversation

@jlc488
Copy link
Copy Markdown
Collaborator

@jlc488 jlc488 commented May 23, 2026

Summary

Promote [Unreleased] to [3.1.0] in both changelogs. No new content — just structural cleanup so the tag v3.1.0 immediately lands on a proper release section.

Changes

  • docs/changelog.md — collapse the (continued) sub-sections (a layering artifact of building the entry in two passes); add explicit Migration guide.
  • docs/changelog.ko.md — same.
  • CHANGELOG.md — top-level summary + link into the docs/changelog detail; add the v3.1.0 footer link.

Test plan

  • CI green (docs-only change, no test or source code touched)
  • After merge: tag v3.1.0 triggers the release workflow → Maven Central publish across 11 modules
  • After Maven Central propagation: bump the 5 ssrf-guard demos in devslab-examples from 3.0.13.1.0 and add the new ssrf-guard-langchain4j-demo

jlc488 added 2 commits May 23, 2026 20:00
[Unreleased] section's accumulated v3.1 entries promoted into a proper
[3.1.0] heading. No content change — just structural cleanup before
tagging:

  - docs/changelog.md       (en, full): collapse the (continued)
                                        sub-sections, add Migration
                                        guide.
  - docs/changelog.ko.md    (ko, full): mirror.
  - CHANGELOG.md            (top-level): condensed summary + link to
                                          the docs/changelog detail.

The tag v3.1.0 follows immediately after this lands on main.
Wire-format coordinates only — Gradle/Maven snippets and 'Replace
3.0.0 with the latest' callouts. Historical references stay intact:
  - 'NEW v3.0.0' annotations (features added in v3.0.0)
  - '[v3.0.0 changelog]#300-...' links (package rename mapping
    lives in the v3.0.0 changelog section)
  - 'Upgrading from v2.0.0?' headers

Also rewords 'ssrf-guard v3.0.0 is split along HTTP-client boundaries'
to 'ssrf-guard 3.0+ is split' — the splitting was introduced in v3.0.0
and persists, so present-tense + '3.0+' is more accurate than pinning
to v3.0.0 in a doc that's read by v3.1.0+ consumers.
@jlc488 jlc488 merged commit 8ae8099 into main May 23, 2026
1 check passed
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