Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: Bump framework.version from 8.26.0 to 8.27.1 #6644

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

chore: Bump framework.version from 8.26.0 to 8.27.1 #6644

wants to merge 2 commits into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 17, 2024

Bumps framework.version from 8.26.0 to 8.27.1.
Updates com.vaadin:vaadin-client from 8.26.0 to 8.27.1

Release notes

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

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 8.27.0 has 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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

    If this is the case, contact Vaadin Support.

  • Updated the license checker, which fixes an issue where licence checking could fail due to an SSL error.

  • Vastly improved the ColorPicker widget, by improving the behavior of its history feature and made it render correctly on Valo-based themes.

  • Improved ComboBox so that it no longer unnecessarily truncates the contents of the popup list.

  • Improved ComboBox popup management. ComboBox should no longer cause constant reflows for updating the popup list position when no repositioning is necessary.

  • Fixed an oversight in the eager UI closing feature of Vaadin Server, where the browser's Beacon API would be attempted to be used to signal to the server that the session can be closed and cleaned up. The original implementation assumed browsers detected as Chrome-based to support the Beacon API, but this was found to not be a correct assumption in testing, so Beacon API availability is now detected dynamically at runtime to avoid a late-stage JavaScript execution fault.

    Also made eager UI closing function on Firefox, which advertises Beacon API availability but does not actually send the message to the server. Firefox was special-cased to use the beforeUnload event instead.

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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

... (truncated)

Changelog

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

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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

    If this is the case, contact Vaadin Support.

  • Updated the license checker, which fixes an issue where licence checking could fail due to an SSL error.

  • Vastly improved the ColorPicker widget, by improving the behavior of its history feature and made it render correctly on Valo-based themes.

  • Improved ComboBox so that it no longer unnecessarily truncates the contents of the popup list.

  • Improved ComboBox popup management. ComboBox should no longer cause constant reflows for updating the popup list position when no repositioning is necessary.

  • Fixed an oversight in the eager UI closing feature of Vaadin Server, where the browser's Beacon API would be attempted to be used to signal to the server that the session can be closed and cleaned up. The original implementation assumed browsers detected as Chrome-based to support the Beacon API, but this was found to not be a correct assumption in testing, so Beacon API availability is now detected dynamically at runtime to avoid a late-stage JavaScript execution fault.

    Also made eager UI closing function on Firefox, which advertises Beacon API availability but does not actually send the message to the server. Firefox was special-cased to use the beforeUnload event instead.

Commits

Updates com.vaadin:vaadin-client-compiler from 8.26.0 to 8.27.1

Release notes

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

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 8.27.0 has 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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

    If this is the case, contact Vaadin Support.

  • Updated the license checker, which fixes an issue where licence checking could fail due to an SSL error.

  • Vastly improved the ColorPicker widget, by improving the behavior of its history feature and made it render correctly on Valo-based themes.

  • Improved ComboBox so that it no longer unnecessarily truncates the contents of the popup list.

  • Improved ComboBox popup management. ComboBox should no longer cause constant reflows for updating the popup list position when no repositioning is necessary.

  • Fixed an oversight in the eager UI closing feature of Vaadin Server, where the browser's Beacon API would be attempted to be used to signal to the server that the session can be closed and cleaned up. The original implementation assumed browsers detected as Chrome-based to support the Beacon API, but this was found to not be a correct assumption in testing, so Beacon API availability is now detected dynamically at runtime to avoid a late-stage JavaScript execution fault.

    Also made eager UI closing function on Firefox, which advertises Beacon API availability but does not actually send the message to the server. Firefox was special-cased to use the beforeUnload event instead.

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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

... (truncated)

Changelog

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

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.

    This is a potentially breaking change if your build expects to have a transitive vaadin-server dependency.

    This change was made in order to make it easier to use the Jakarta versions of the server and push packages, namely vaadin-server-mpr-jakarta, vaadin-compatibility-server-mpr-jakarta and vaadin-push-jakarta, as they provide the same API and class structure but rely on the Jakarta namespace instead of Javax.

  • Improved change detection of Binder. This is a backport from Flow pull request #19488 which fixes Flow issue #19260.

    In short, previously a reverted change to a bound field would still be considered a change. With this change, the meaningfulness of the value changes is considered.

  • Fixed an issue in Binder where calling binder.removeBinding() could result in a null pointer exception down the line, as the removed binding was not also removed from the changedBindings list.

    This is a backport of Flow pull request #6827 which fixes Flow issue #5384.

  • Changed the internal LayoutManager.layoutLater method to use requestAnimationFrame instead of a timer with a magic 100 msec timeout value to improve rendering performance and stability. We have not detected any breakage with this change, but it should nonetheless be considered a potentially breaking change, as if your client-side code for whatever reason relies on the presence of that 100 msec timer between layout cycles, you may experience rendering instability.

    If this is the case, contact Vaadin Support.

  • Updated the license checker, which fixes an issue where licence checking could fail due to an SSL error.

  • Vastly improved the ColorPicker widget, by improving the behavior of its history feature and made it render correctly on Valo-based themes.

  • Improved ComboBox so that it no longer unnecessarily truncates the contents of the popup list.

  • Improved ComboBox popup management. ComboBox should no longer cause constant reflows for updating the popup list position when no repositioning is necessary.

  • Fixed an oversight in the eager UI closing feature of Vaadin Server, where the browser's Beacon API would be attempted to be used to signal to the server that the session can be closed and cleaned up. The original implementation assumed browsers detected as Chrome-based to support the Beacon API, but this was found to not be a correct assumption in testing, so Beacon API availability is now detected dynamically at runtime to avoid a late-stage JavaScript execution fault.

    Also made eager UI closing function on Firefox, which advertises Beacon API availability but does not actually send the message to the server. Firefox was special-cased to use the beforeUnload event instead.

Commits

Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
com.vaadin:vaadin-client [>= 8.16.a, < 8.17]
com.vaadin:vaadin-client-compiler [>= 8.16.a, < 8.17]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
chore: Bump framework.version from 8.26.0 to 8.27.1
63ba6c6 
Bumps `framework.version` from 8.26.0 to 8.27.1.

Updates `com.vaadin:vaadin-client` from 8.26.0 to 8.27.1
- [Release notes](https://github.com/vaadin/framework/releases)
- [Changelog](https://github.com/vaadin/framework/blob/master/CHANGELOG-VAADIN8.md)
- [Commits](vaadin/framework@8.26.0...8.27.1)

Updates `com.vaadin:vaadin-client-compiler` from 8.26.0 to 8.27.1
- [Release notes](https://github.com/vaadin/framework/releases)
- [Changelog](https://github.com/vaadin/framework/blob/master/CHANGELOG-VAADIN8.md)
- [Commits](vaadin/framework@8.26.0...8.27.1)

---
updated-dependencies:
- dependency-name: com.vaadin:vaadin-client
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.vaadin:vaadin-client-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Sep 17, 2024
@dependabot dependabot bot mentioned this pull request Sep 17, 2024
Closed
@sonarcloud SonarCloud
Copy link

sonarcloud bot commented Sep 17, 2024

Quality Gate Passed 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 SonarCloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@web-padawan