Update vaadin.version to v25.1.0

[xdev-renovate]

This PR contains the following updates:

Package	Type	Update	Change
com.vaadin:vaadin-bom (source)	import	minor	25.0.7 → 25.1.0
com.vaadin:vaadin-maven-plugin (source)	build	minor	25.0.7 → 25.1.0

---

Release Notes

vaadin/platform (com.vaadin:vaadin-bom)

v25.1.0: Vaadin 25.1.0

Compare Source

Upgrading · Docs · Get Started

Notable Changes in Vaadin 25.1

1. UI State Management with Signals (Flow)

Vaadin 25.1 introduces Signals to handle UI state in Flow. This enables cleaner code with a single source of truth for each component property.

Versatile Signal Types

Signal instances hold UI state values and automatically track which components need updating when a signal value changes.

• Local signals: For a view’s or component’s internal state.
• Shared signals: For sharing state with other users in real time.
• Computed signals: For deriving values based on other signals.

Signal Bindings

New bindXyz methods are available for all components to automatically update properties based on signal changes. Examples include:

• Generic features: bindVisible
• Component-specific properties: bindMin in Date Picker
• Two-way bindings: bindValue for all input fields

---

2. New UI Components (Preview)

[!NOTE]
These components are preview releases and can be enabled using feature flags.

Slider & RangeSlider

New slider input components for selecting:

• A single value (Slider)
• Two values from a range (RangeSlider)

Badge

A new component for displaying statuses and notification indicators. Visual variants include:

• Icon-only, Number-only, and Dot
• Multiple color options

AI Integration

New Flow features for integrating AI-powered functionality into Vaadin apps:

• AIOrchestrator: Manages interactions between UI components and LLMs.
• LLM Providers: Out-of-the-box implementations for Spring AI and LangChain4j.

Upload Components

New standalone components for flexible file upload UIs:

• UploadButton
• UploadDropZone
• UploadFileList (includes a thumbnail-bar style variant)

---

3. Aura Theme Enhancements

The new Aura theme, introduced in V25, receives major updates in this beta, including previously missing component style variants and a refreshed default color palette.

---

4. Component Enhancements

Common Variant Entries

Component style variants that work in both Aura and Lumo themes now have common, unprefixed entries in the *Variant classes.

• Example: ButtonVariant.PRIMARY

Key Updates by Component

Component	New Feature / Improvement
Message List	Support for file attachments and automatic "snap to bottom" scrolling.
Map	Support for drawing lines and a configurable scale indicator.
Spreadsheet	Support for text colors in custom number formats.
Dialog	New keepInViewport option to prevent dragging outside the visible area.
Grid	New scrollToColumn API.

---

5. 🎨 Major Vaadin Copilot Redesign

Vaadin Copilot has been completely overhauled with a streamlined look and improved workflow.

New Toolbar & Working Modes

The traditional Vaadin button and drawers have been replaced with a modern toolbar featuring four operational modes:

• Play Mode: Copilot is idle and does not affect the running application.
• Inspect Mode: Read-only tools for inspecting application structure.
• Test Mode: Tools for accessibility checks and UI test generation.
• Edit Mode: Drag-and-drop UI modification, copy-paste, and AI-powered features.

Redesigned Panels & Settings

• Modern Aesthetic: Most internal panels now feature a consistent look for improved usability.
• Settings Panel: Copilot is now customizable via a new dedicated Settings interface.

Expanded Access

All premium features—including source code manipulation and AI—are now available to any user with an active Vaadin.com account. Users simply need to log in via the toolbar to unlock these capabilities.

Changelogs

• Flow (25.1.0) and Hilla (25.1.0)
• Design System
  • Web Components (25.1.0)
  • Flow Components (25.1.0)
• TestBench (10.1.0)
• Browserless Test(1.0.0)
• Feature Pack(25.0.0)
• Modernization Toolkit (Documentation)
  • Feature Pack (Documentation)
  • Dragonfly (Documentation)
  • Modernization Toolkit Analyzer (Analyzer for Eclipse, Analyzer for Maven)
• Multiplatform Runtime (MPR) (8.0.1)
• Router (2.0.1)
• Vaadin Kits
  • AppSec Kit (4.0.1)
  • Azure Kit (1.0.0)
  • Collaboration Engine (7.0.0)
  • Copilot (25.1.0)
  • Kubernetes Kit (3.1.0)
  • Observability Kit (4.0.0)
  • SSO Kit (4.1.0)
  • Swing Kit (3.0.1)

Official add-ons and plugins:

• Spring add-on (25.1.0)
• CDI add-on (16.0.0)
• Maven plugin (25.1.0)
• Gradle plugin (25.1.0)
• Quarkus plugin (3.1.0)

Upgrading guides

• Upgrading to Vaadin 25

Support

Vaadin 25 is the latest stable version, with extended support options available (release model).

Supported technologies

Desktop browser	Chrome (evergreen). Firefox (evergreen). Firefox Extended Support Release (ESR). Safari 17 or newer (latest minor version in each major series). Edge (Chromium, evergreen).
Mobile browser	Chrome (evergreen) for Android (4.4 or newer). Safari 17 for iOS or newer (latest minor version in each major series).
Development OS	Windows macOS Linux
IDE	Any IDE or editor that works with the language of your choice should work well. Our teams often use IntelliJ, Eclipse, VS Code among others. Vaadin IDE plugins (IntelliJ and VS Code) support the IDE versions released during the last 12 months Vaadin Designer supports the following IDEs (Note, Vaadin Designer has been deprecated since Vaadin 25): Eclipse from Photon and upwards JetBrains IntelliJ IDEA from 2017 upwards
Java	Version 21 of any JDK or JRE
Maven	Version 3.8 or newer
Gradle	Version 8.14 or newer
Application server	Vaadin Flow requires Java Servlet API 6.1 and Java 21 or newer. It is tested on: Apache Tomcat 11 Open Liberty 23 RedHat JBoss EAP 8.1 To work with RedHat JBoss EAP 8.0, the following content needs to be added under WEB-INF folder as jboss-deployment-structure.xml Workaround for supporting RedHat JBoss EAP 8.0 <jboss-deployment-structure> <deployment> <exclude-subsystems> <subsystem name="jaxrs" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> WildFly 36 + WildFly 39 is compatible with Vaadin 25. But WildFly 36.x, 37.x, 38.x are using a conflict version of Jackson 2, in order to work with Vaadin 25, the following content needs to be added under WEB-INF folder as jboss-deployment-structure.xml Workaround for supporting WildFly 36 <jboss-deployment-structure> <deployment> <exclude-subsystems> <subsystem name="jaxrs" /> </exclude-subsystems> </deployment> </jboss-deployment-structure> Workaround for supporting WildFly 37-38 <jboss-deployment-structure> <deployment> <exclusions> <module name="com.fasterxml.jackson.core.jackson-annotations"/> </exclusions> </deployment> </jboss-deployment-structure> Jetty 12 Payara Server 6 Payara Micro 6
Node.js	Version 24
Spring Boot	Version 4.0.4+
Quarkus	latest LTS (3.32) or newer

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.