Install open-java-format 2.98.0.4, which ships the Migrate changes

2.98.0.4 is out on GitHub, Maven Central and the Gradle Plugin Portal,
so the pages now install it. It carries the three output changes that
Migrate listed as not yet in a release: the cast fix
(openjavaformat/open-java-format#78), the switch expression on the
declaration's line (openjavaformat/open-java-format#76) and the /***
banner that no longer counts as javadoc
(openjavaformat/open-java-format#74). Each now says it applies since
2.98.0.4, and the corpus paragraph no longer calls them unreleased.

The GitHub Action page keeps 2.98.0.3 as the default of the action's
version input, because the action itself still defaults to it.

Author: abashev

docs/migrate.md

@@ -8,22 +8,21 @@ produces no formatting diff and needs no reformatting commit.
 
 - Since 2.98.0.3: a long string is no longer split after an escaped backslash followed by `n`, as if
   that were a line break, and imports with comments between them are formatted rather than rejected.
-- Not yet in a release: a cast to a parameterized type at the end of a call chain is no longer split
+- Since 2.98.0.4: a cast to a parameterized type at the end of a call chain is no longer split
   inside its type, `(PrivilegedAction<` on one line and `String>)` on the next, when the chain is
   inlined but the type does not fit behind it. The call breaks its arguments one per line instead.
-- Not yet in a release: a switch expression that initializes a variable or a field starts on the line
-  of the declaration, `int x = switch (y) {`, with its cases eight columns further left, the shape a
+- Since 2.98.0.4: a switch expression that initializes a variable or a field starts on the line of
+  the declaration, `int x = switch (y) {`, with its cases eight columns further left, the shape a
   plain assignment already had. This is the one change of palantir-java-format 2.99.0, brought over.
-- Not yet in a release: a comment that opens with `/***`, such as a banner, no longer counts as
-  javadoc, so a blank line between it and the declaration after it stays, as after any other block
-  comment.
+- Since 2.98.0.4: a comment that opens with `/***`, such as a banner, no longer counts as javadoc,
+  so a blank line between it and the declaration after it stays, as after any other block comment.
 
 Checked on 341 source files, about 24,000 lines: palantir-java-format 2.98.0 and open-java-format
 2.98.0.2 give byte-identical output. On the JDK 21 sources, 2.98.0.3 reformats 5 of the files that
-2.98.0.2 leaves unchanged when run again, all because of the string fix. Of the three unreleased
-changes, the cast fix changes one statement, in `sun.rmi.transport.tcp.TCPTransport`; the switch
-change moves 57 declarations in 51 files; and the banner change keeps 70 blank lines in 43 files,
-every one of them present in the source.
+2.98.0.2 leaves unchanged when run again, all because of the string fix. In 2.98.0.4 the cast fix
+changes one statement, in `sun.rmi.transport.tcp.TCPTransport`; the switch change moves 57
+declarations in 51 files; and the banner change keeps 70 blank lines in 43 files, every one of them
+present in the source.
 
 The Java packages are unchanged as well. Only the names in your build and your scripts change.
 

zensical.toml

@@ -105,7 +105,7 @@ toggle.name = "Switch to system preference"
 # plugin puts it in before the Markdown is rendered, so it lands in code blocks too. The key is not
 # extra.version: the theme reads that one as the switch for a version selector.
 [project.extra]
-ojf_version = "2.98.0.3"
+ojf_version = "2.98.0.4"
 
 # Renders every page as a Jinja template, for {{ ojf_version }}. A misspelt variable or a stray {{
 # fails the build instead of leaving a gap or the raw text on the site.