You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,12 @@
2
2
3
3
Status of the `main` branch. Changes prior to the next official version change will appear here.
4
4
5
+
* General:
6
+
- Breaking change in mode definitions: Projects (project.yml) can no longer override `base_modes`.
7
+
Instead, they can define `added_modes` to add modes on top of base and default modes.
8
+
See updated [documentation on modes](https://oraios.github.io/serena/02-usage/050_configuration.html#modes).
9
+
- Serena's default configuration now uses `interactive` and `editing` as `base_modes` instead of as `default_modes`.
10
+
5
11
* Language Servers:
6
12
- Java (`eclipse.jdt.ls`): Add upstream JDTLS mode for offline / restricted-network use. Setting both `jdtls_path` and `lombok_path` in `ls_specific_settings.java` makes Serena use an existing upstream JDTLS installation (e.g. `brew install jdtls`) and the system JDK 21+, skipping the ~500 MB vscode-java VSIX, Gradle, and IntelliCode downloads. New related setting `java_home` lets the user override the JDK used to launch JDTLS. Default behavior unchanged — the JDTLS workspace hash is preserved bit-for-bit for users on the default route, so existing project caches are reused without a one-time reindex; the launcher path is mixed into the hash only when `jdtls_path` is set, isolating upstream installations from the default workspace. #1415
0 commit comments