build(deps): bump cia.project.versions.vaadin from 8.14.4 to 8.27.5

[dependabot]

Bumps cia.project.versions.vaadin from 8.14.4 to 8.27.5.
Updates com.vaadin:vaadin-themes from 8.14.4 to 8.27.5

Release notes

Sourced from com.vaadin:vaadin-themes's releases.

Vaadin Framework 8.27.5 is an Extended Maintenance patch release with the following changes:

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin Framework 8.27.4 is an Extended Maintenance patch release with the following changes:

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin Framework 8.27.3 is an Extended Maintenance patch release with the following changes:

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin Framework 8.27.2 is an Extended Maintenance patch release with the following changes:

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin Framework 8.27.1 is an Extended Maintenance hotfix release with the following changes:

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin Framework 8.27.0 is an Extended Maintenance feature release with the following changes:

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Changelog

Sourced from com.vaadin:vaadin-themes's changelog.

Vaadin 8.27.5

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin 8.27.4

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin 8.27.3

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin 8.27.2

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin 8.27.1

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin 8.27.0

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Commits

• 3fa2160 chore: Update changelog for Vaadin 8.27.5
• 08c14bb chore: Update changelog for Vaadin 8.27.4 (#12639)
• 504ce43 chore: Add a very visible obsoletion message (#12634)
• 72f83d7 feat: Update POMs and bump build dependency versions (#12636)
• e0e2268 chore: Downgrade snapshot version for free version (#12635)
• d1d6e2f chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.3 (#12633)
• 6cf2a5c chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.2 (#12632)
• 972ed98 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.1 (#12631)
• aad11f8 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.0 (#12630)
• 9bc9043 chore: Simplify license information in README (#12629)
• Additional commits viewable in compare view

Updates com.vaadin:vaadin-compatibility-server from 8.14.4 to 8.27.5

Release notes

Sourced from com.vaadin:vaadin-compatibility-server's releases.

Vaadin Framework 8.27.5 is an Extended Maintenance patch release with the following changes:

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin Framework 8.27.4 is an Extended Maintenance patch release with the following changes:

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin Framework 8.27.3 is an Extended Maintenance patch release with the following changes:

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin Framework 8.27.2 is an Extended Maintenance patch release with the following changes:

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin Framework 8.27.1 is an Extended Maintenance hotfix release with the following changes:

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin Framework 8.27.0 is an Extended Maintenance feature release with the following changes:

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Changelog

Sourced from com.vaadin:vaadin-compatibility-server's changelog.

Vaadin 8.27.5

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin 8.27.4

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin 8.27.3

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin 8.27.2

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin 8.27.1

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin 8.27.0

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Commits

• 3fa2160 chore: Update changelog for Vaadin 8.27.5
• 08c14bb chore: Update changelog for Vaadin 8.27.4 (#12639)
• 504ce43 chore: Add a very visible obsoletion message (#12634)
• 72f83d7 feat: Update POMs and bump build dependency versions (#12636)
• e0e2268 chore: Downgrade snapshot version for free version (#12635)
• d1d6e2f chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.3 (#12633)
• 6cf2a5c chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.2 (#12632)
• 972ed98 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.1 (#12631)
• aad11f8 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.0 (#12630)
• 9bc9043 chore: Simplify license information in README (#12629)
• Additional commits viewable in compare view

Updates com.vaadin:vaadin-maven-plugin from 8.14.3 to 8.27.5

Commits

• ebc6fa7 fix: get framework version from runtime vaadin-server variant (#144)
• 4537b70 chore: Update plexus-archiver version (#142)
• cc38257 fix: Allow both development and release license types at compile time (#140)
• 6172614 Always check license when compiling, use new license checker (#136)
• See full diff in compare view

Updates com.vaadin:vaadin-server from 8.14.4 to 8.27.5

Release notes

Sourced from com.vaadin:vaadin-server's releases.

Vaadin Framework 8.27.5 is an Extended Maintenance patch release with the following changes:

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin Framework 8.27.4 is an Extended Maintenance patch release with the following changes:

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin Framework 8.27.3 is an Extended Maintenance patch release with the following changes:

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin Framework 8.27.2 is an Extended Maintenance patch release with the following changes:

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin Framework 8.27.1 is an Extended Maintenance hotfix release with the following changes:

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin Framework 8.27.0 is an Extended Maintenance feature release with the following changes:

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Changelog

Sourced from com.vaadin:vaadin-server's changelog.

Vaadin 8.27.5

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin 8.27.4

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin 8.27.3

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin 8.27.2

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin 8.27.1

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin 8.27.0

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Commits

• 3fa2160 chore: Update changelog for Vaadin 8.27.5
• 08c14bb chore: Update changelog for Vaadin 8.27.4 (#12639)
• 504ce43 chore: Add a very visible obsoletion message (#12634)
• 72f83d7 feat: Update POMs and bump build dependency versions (#12636)
• e0e2268 chore: Downgrade snapshot version for free version (#12635)
• d1d6e2f chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.3 (#12633)
• 6cf2a5c chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.2 (#12632)
• 972ed98 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.1 (#12631)
• aad11f8 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.0 (#12630)
• 9bc9043 chore: Simplify license information in README (#12629)
• Additional commits viewable in compare view

Updates com.vaadin:vaadin-client-compiled from 8.14.4 to 8.27.5

Release notes

Sourced from com.vaadin:vaadin-client-compiled's releases.

Vaadin Framework 8.27.5 is an Extended Maintenance patch release with the following changes:

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin Framework 8.27.4 is an Extended Maintenance patch release with the following changes:

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin Framework 8.27.3 is an Extended Maintenance patch release with the following changes:

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin Framework 8.27.2 is an Extended Maintenance patch release with the following changes:

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin Framework 8.27.1 is an Extended Maintenance hotfix release with the following changes:

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin Framework 8.27.0 is an Extended Maintenance feature release with the following changes:

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Changelog

Sourced from com.vaadin:vaadin-client-compiled's changelog.

Vaadin 8.27.5

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin 8.27.4

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin 8.27.3

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin 8.27.2

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

• Improved initialization of the eager unload feature when using Firefox, Safari or any iOS browser.

  PLEASE NOTE: this feature will make the "are you sure you want to leave" confirmation not function as intended, as these browsers need to hook onto the beforeunload event. This will cause the session to become invalidated and will require reloading the page even if the user decides to stay. If you need to disable the eager unload functionality for Safari/Firefox/iOS in order to display the confirmation, directly assign a handler to window.onbeforeunload with a JavaScript call.

Vaadin 8.27.1

• Fixed an issue with the vaadin-push packaging which prevented the JavaScript payload from loading.
• Internal test fixes

Vaadin 8.27.0

• Added vaadin-push-jakarta package for a Jakarta-based Push implementation, based on Atmosphere 3. This package is meant to be used together with the vaadin-server-mpr-jakarta and vaadin-compatibility-server-mpr-jakarta packages in environments like Spring 6+ and Jetty 11+.

  This feature is to be considered experimental for the moment; please report any and all issues you encounter with it to Vaadin Support.

• Altered packaging of vaadin-client, vaadin-compatibility-client and vaadin-client-compiler packages to have the vaadin-server and vaadin-compatiblity-server dependencies with provided scope.

... (truncated)

Commits

• 3fa2160 chore: Update changelog for Vaadin 8.27.5
• 08c14bb chore: Update changelog for Vaadin 8.27.4 (#12639)
• 504ce43 chore: Add a very visible obsoletion message (#12634)
• 72f83d7 feat: Update POMs and bump build dependency versions (#12636)
• e0e2268 chore: Downgrade snapshot version for free version (#12635)
• d1d6e2f chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.3 (#12633)
• 6cf2a5c chore: Update CHANGELOG-VAADIN8.md for Vaadin 8.27.2 (#12632)
• 972ed98 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.1 (#12631)
• aad11f8 Update CHANGELOG-VAADIN8.md for Vaadin 8.27.0 (#12630)
• 9bc9043 chore: Simplify license information in README (#12629)
• Additional commits viewable in compare view

Updates com.vaadin:vaadin-client from 8.14.4 to 8.27.5

Release notes

Sourced from com.vaadin:vaadin-client's releases.

Vaadin Framework 8.27.5 is an Extended Maintenance patch release with the following changes:

• Fixed an issue where exceptions might not be properly processed as a component is being detached. Exceptions are now caught both when handling the detach event and when calling detach manually. The detach event now fires reliably when the connector tracker is updated even when an exception occurs during detach.

• Altered handling of the eager UI cleanup feature to not use the beforeunload event as a workaround on Safari. Safari will instead use the default pagehide event to listen for imminent UI disposal. Using the beforeunload event caused an issue where resource links would erroneously be treated as navigation away from the current UI, causing the UI to be invalidated.

  Firefox and Internet Explorer still use the beforeunload event to signal cleanup for the UI.

Vaadin Framework 8.27.4 is an Extended Maintenance patch release with the following changes:

• Added feature to automatically resume Push connection when a client unexpectedly loses communication with the server. Pending Push messages are now cached on the server until the session times out or connectivity is restored for a better user experience.

  This is a backport of Flow pull request #20283.

• Fixed Framework issue #11699. Previously, calling UI.getCurrent() inside a UI.access() callback could return a random UI instance under certain circumastances. CurrentInstance is now properly cleared before the current session reference is set before running any pending access callbacks.

  This is a backport of Flow pull request #20255.

• Moved (some) blocking calls outside of session lock. Fixes a potential deadlock issue.

  This is a backport of Flow pull request #20475.

• Specified pointer-events: auto as default for overlay containers in the Valo theme. This fixes an edge case where users were unable to select values from V8 comboboxes placed inside a V14 Dialog component when running under the Vaadin Multi Platform Runtime.

Vaadin Framework 8.27.3 is an Extended Maintenance patch release with the following changes:

• Added an option to disable Push disconnect on refresh. This is a special-case workaround. Normally when UI is refreshed when @PreserveOnRefresh is used, UI checks if an associated Push connection is active and disconnects it in order to avoid a race condition. This functionality was originally introduced to fix Framework [issue #12577](vaadin/framework#12577). However, with some containers such as Payara this can have unwanted side effects, such as CDI reporting that no session scoped context is available after refresh.

  This feature can now be toggled off using the protected UI method setDisconnectPushOnRefresh(false).

• Updated Atmosphere to detect Payara alongside Glassfish and enable async support for it. This is a workaround for a bug/feature that exists both in Glassfish and Payara that provides a null ServerContainer reference that would otherwise cause initialization to fail.

Vaadin Framework 8.27.2 is an Extended Maintenance patch release with the following changes:

• Included the vaadin-portlet package in the Vaadin 8 BOM. As a result, the version of the vaadin-portlet package does not need to be defined if the vaadin-bom artifact is imported. This definition was originally left out due to an oversight and the omission was discovered during internal manual testing.

  Description has been truncated

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 1 package(s) with unknown licenses.

See the Details below.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA a9603f8.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

License Issues

web-widgets/pom.xml

Package	Version	License	Issue Type
com.vaadin:vaadin-maven-plugin	8.27.5	Null	Unknown License

OpenSSF Scorecard

Package	Version	Score	Details
maven/com.vaadin:vaadin-maven-plugin	8.27.5	Unknown	Unknown

Scanned Files

• web-widgets/pom.xml

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.