v2.6.0
[34mINFO[0m Using node as runtime [34mINFO[0m node version to use: v25.2.1 [34mINFO[0m node version v25.2.1 already exists in cache [34mINFO[0m Package Manager detected: pnpm [34mINFO[0m pnpm version * is already installed in /home/runner/.local/share/gnpm/_gnpm/pnpm-10.22.0 [34mINFO[0m Get all paths to link to: /home/runner/.local/share/gnpm/_gnpm/pnpm [34mINFO[0m Package manager pnpm installed at [/home/runner/.local/share/gnpm/_gnpm/pnpm] [34mINFO[0m Running command with package manager: pnpm
bin@2.6.0 generateChangelog /home/runner/work/etherpad-lite/etherpad-lite/bin node --import tsx generateReleaseNotes.ts refs/tags/v2.6.0
- Added native option to transfer your Etherpad session between browsers. If you use multiple browsers or different PC for Etherpad they are different sessions. Meaning typing on one PC and then switching to another one in the same pad will result in different authorship colors. With this new feature you can now transfer your session to another browser or PC. To do so, open the home page and click on the wheel icon in the top right corner. After that click through the first dialog prompting you to copy a code to your clipboard. On your second browser open the same dialog and switch to "Receive Session" tab. There you can paste the code you copied before and click on "Receive Session". After that your session is transferred, and you can continue editing with the same authorship color as before. Just be aware that you can't have two active sessions at once in a pad.
- Updated to oidc provider v2.6.0 after resolving compatibility issues.
🎉 For all the people celebrating: Have a happy and awesome new year! 🎉 There is something big on the horizon for Etherpad in 2026. Stay tuned!
v2.5.2
- Fixes the no skin theme having an overlapping
- Adds a new setting to disable recent pads to be shown. By setting
showRecentPadsto false in thesettings.jsonfile you can disable the recent pads feature on the home screen. - Sets the oidc-provider version to 9.5.1 as 9.5.2 crashes Etherpad on startup.
v2.5.1
-
Added endpoint for prometheus scraping. You can now scrape the metrics endpoint with prometheus. It is available at /stats/prometheus if you have enableMetrics set to true in your settings.json
-
fixed exposeVersion causing the pad panel to not load correctly
-
fixed admin manage pad url to also take the base path into account
v2.5.0
bin@2.5.0 generateChangelog D:\a\etherpad-lite\etherpad-lite\bin node --import tsx generateReleaseNotes.ts "refs/tags/v2.5.0"
- Updated to express 5.0.0. This is a major update to express that brings a lot of improvements and fixes. Please update all your plugins to the latest version to ensure compatibility. A lot changed in the route matching, and thus old plugins will throw errors and crash Etherpad.
- Fixed an issue with the no-skin theme with cookie recentPadList feature
- Fixed layout issues with the no-skin theme
v2.3.0
- Added possibility to cluster Etherpads behind reverse proxy. There is now a new reverse proxy designed for Etherpads that handles multiple Etherpads and the created pads in them. It will assign the pad assignement to an Etherpad at random but once the choice was made it will always reverse proxy the same backend. This allows to host multiple concurrent Etherpads and benefit from multi core systems even though one Etherpad is singlethreaded.
- Added reverse proxy configuration for replacing Nginx. In the past there were some issues with nginx and its configuration. This reverse proxy allows you to handle your configuration with ease.
If you want to find out more about the reverse proxy method check out the repository https://github.com/ether/etherpad-proxy . It also contains a sample docker-compose file with three Etherpads and one etherpad-proxy. Of course you need to adapt the settings.json.template to your liking and map it into the reverse proxy image before you are ready :).
- Added client authorization to work with Etherpad. Before it would get blocked because it doesn't have the required claim. As this is now fixed etherpad-proxy can also work with your new OAuth2 configuration and retrieve a token via client credentials flow.