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

Bump auto-value.version from 1.10.1 to 1.10.2 #1145

Closed
wants to merge 1 commit into from
Closed

Bump auto-value.version from 1.10.1 to 1.10.2 #1145

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 24, 2023

Bumps auto-value.version from 1.10.1 to 1.10.2.
Updates com.google.auto.value:auto-value-annotations from 1.10.1 to 1.10.2

Release notes

Sourced from com.google.auto.value:auto-value-annotations's releases.

AutoValue 1.10.2

  • The constructor parameter names in the class generated by @Memoized no longer add a $. This may require changes to code that was depending on the old names, for example using Error Prone's /* param= */ comments. (4f8dbea8a)
  • An AutoValue or AutoBuilder property is now allowed to be null if its type is a type variable with a @Nullable bound, like <T extends @Nullable Object>. (1b58cff5e)
  • Better error message when AutoValue, AutoBuilder, etc give up because of missing types. We now say what the first missing type was. (2e734f605)
  • AutoBuilder copy-constructors no longer require an exact match between a property and the corresponding constructor parameter. (1440a25e4)
  • A property of type List<T> can be built by a property builder whose build() method returns List<? extends T>. (8ba4531b8)
  • Made it easier to support @CopyAnnotations in AutoValue extensions, via new methods classAnnotationsToCopy and methodAnnotationsToCopy. (a3f218d2b)
  • Generated builders now include a @Nullable type annotation on appropriate builder fields if one is available. (91d5f32c6)
  • Updated @AutoAnnotation documentation to say that it isn't needed in Kotlin. (600b4b6d0)
  • Maven dependencies have been updated, fixing #1532.
Commits
  • c11df8e Set version number for auto-value-parent
  • ac6de46 Skip maven-gpg-plugin in the gwtserializer module.
  • 7d93867 Fix a StackOverflowError in getLocalAndInheritedMethods, involving recurs...
  • 39743a8 Add a test method that reproduces an infinite recursion.
  • c3f22dc Bump maven-shade-plugin from 3.4.1 to 3.5.0 in /value
  • bd89167 Bump errorprone.version from 2.19.1 to 2.20.0 in /value
  • 1c4a65e Update to the latest ECJ (Eclipse compiler).
  • 242ef10 Bump truth from 1.1.4 to 1.1.5 in /factory
  • ee2cf8d Uglify the AutoFactory javadoc to work around bugs in older javadoc versions.
  • d4b2d06 Bump truth.version from 1.1.4 to 1.1.5 in /value
  • Additional commits viewable in compare view

Updates com.google.auto.value:auto-value from 1.10.1 to 1.10.2

Release notes

Sourced from com.google.auto.value:auto-value's releases.

AutoValue 1.10.2

  • The constructor parameter names in the class generated by @Memoized no longer add a $. This may require changes to code that was depending on the old names, for example using Error Prone's /* param= */ comments. (4f8dbea8a)
  • An AutoValue or AutoBuilder property is now allowed to be null if its type is a type variable with a @Nullable bound, like <T extends @Nullable Object>. (1b58cff5e)
  • Better error message when AutoValue, AutoBuilder, etc give up because of missing types. We now say what the first missing type was. (2e734f605)
  • AutoBuilder copy-constructors no longer require an exact match between a property and the corresponding constructor parameter. (1440a25e4)
  • A property of type List<T> can be built by a property builder whose build() method returns List<? extends T>. (8ba4531b8)
  • Made it easier to support @CopyAnnotations in AutoValue extensions, via new methods classAnnotationsToCopy and methodAnnotationsToCopy. (a3f218d2b)
  • Generated builders now include a @Nullable type annotation on appropriate builder fields if one is available. (91d5f32c6)
  • Updated @AutoAnnotation documentation to say that it isn't needed in Kotlin. (600b4b6d0)
  • Maven dependencies have been updated, fixing #1532.
Commits
  • c11df8e Set version number for auto-value-parent
  • ac6de46 Skip maven-gpg-plugin in the gwtserializer module.
  • 7d93867 Fix a StackOverflowError in getLocalAndInheritedMethods, involving recurs...
  • 39743a8 Add a test method that reproduces an infinite recursion.
  • c3f22dc Bump maven-shade-plugin from 3.4.1 to 3.5.0 in /value
  • bd89167 Bump errorprone.version from 2.19.1 to 2.20.0 in /value
  • 1c4a65e Update to the latest ECJ (Eclipse compiler).
  • 242ef10 Bump truth from 1.1.4 to 1.1.5 in /factory
  • ee2cf8d Uglify the AutoFactory javadoc to work around bugs in older javadoc versions.
  • d4b2d06 Bump truth.version from 1.1.4 to 1.1.5 in /value
  • Additional commits viewable in compare view

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 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
Bump auto-value.version from 1.10.1 to 1.10.2
a4a952d 
Bumps `auto-value.version` from 1.10.1 to 1.10.2.

Updates `com.google.auto.value:auto-value-annotations` from 1.10.1 to 1.10.2
- [Release notes](https://github.com/google/auto/releases)
- [Commits](google/auto@auto-value-1.10.1...auto-value-1.10.2)

Updates `com.google.auto.value:auto-value` from 1.10.1 to 1.10.2
- [Release notes](https://github.com/google/auto/releases)
- [Commits](google/auto@auto-value-1.10.1...auto-value-1.10.2)

---
updated-dependencies:
- dependency-name: com.google.auto.value:auto-value-annotations
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: com.google.auto.value:auto-value
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jul 24, 2023
cpovirk added a commit that referenced this pull request Jul 24, 2023
@cpovirk
Bump a bunch of deps at once.
120cb1b 
Notes:

- The GWT bump requires changing the browser setting from "FF38" to "FF."
- I skipped the `jsinterop-annotations` bump to 2.1.0 because it's built
  with `-target 11`, while we still support 8.
  (Closes #1147)
  (I've noted this in google/guava#6614)
- The command I used is:
  ```
  mvn org.codehaus.mojo:versions-maven-plugin:2.16.0:{update-properties,use-latest-releases} -DgenerateBackupPoms=false -Dexcludes=com.google.guava:guava
  ```
  That tried to update protobuf to a release candidate. I had thought
  that perhaps this was the result of [a protobuf change from "-rc1" to
  "-rc-1"](protocolbuffers/protobuf#6522), but
  I'm wondering if it's actually just that `versions-maven-plugin` (in
  contrast to Dependabot) counts release candidates [as
  releases](https://www.mojohaus.org/versions/versions-maven-plugin/use-latest-releases-mojo.html)?
  I'd have to investigate further and perhaps [use
  `rulesUri`](https://stackoverflow.com/a/46935363/28465). But since we
  normally rely on Dependabot (and I was using `versions-maven-plugin`
  here only "to make things easier"... :)), I'm not going to worry about
  it now.
  ...
  Also, it looks like protobuf 4 might remove the `hasPresence()` method
  that we'd migrated to back in cl/508716698. If so, there's a good
  chance that the protobuf team will fix things for us :) If not, I'm
  assuming that this will relate to
  ["Editions."](https://protobuf.dev/editions/overview/)

Fixes #1149
Fixes #1148
Fixes #1146
Fixes #1145
@cpovirk cpovirk mentioned this pull request Jul 24, 2023
Closed
copybara-service bot pushed a commit that referenced this pull request Jul 24, 2023
@cpovirk
Bump a bunch of deps at once.
f2717d1 
Notes:

- The GWT bump requires changing the browser setting from "FF38" to "FF."
- I skipped the `jsinterop-annotations` bump to 2.1.0 because it's built
  with `-target 11`, while we still support 8.
  (Closes #1147)
  (I've noted this in google/guava#6614)
- The command I used is:
  ```
  mvn org.codehaus.mojo:versions-maven-plugin:2.16.0:{update-properties,use-latest-releases} -DgenerateBackupPoms=false -Dexcludes=com.google.guava:guava
  ```
  That tried to update protobuf to a release candidate. I had thought
  that perhaps this was the result of [a protobuf change from "-rc1" to
  "-rc-1"](protocolbuffers/protobuf#6522), but
  I'm wondering if it's actually just that `versions-maven-plugin` (in
  contrast to Dependabot) counts release candidates [as
  releases](https://www.mojohaus.org/versions/versions-maven-plugin/use-latest-releases-mojo.html)?
  I'd have to investigate further and perhaps [use
  `rulesUri`](https://stackoverflow.com/a/46935363/28465). But since we
  normally rely on Dependabot (and I was using `versions-maven-plugin`
  here only "to make things easier"... :)), I'm not going to worry about
  it now.
  ...
  Also, it looks like protobuf 4 might remove the `hasPresence()` method
  that we'd migrated to back in cl/508716698. If so, there's a good
  chance that the protobuf team will fix things for us :) If not, I'm
  assuming that this will relate to
  ["Editions."](https://protobuf.dev/editions/overview/)

Fixes #1149
Fixes #1148
Fixes #1146
Fixes #1145

Fixes #1150

RELNOTES=n/a
PiperOrigin-RevId: 550553262
@copybara-service copybara-service bot mentioned this pull request Jul 24, 2023
Closed
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 24, 2023

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.

@dependabot dependabot bot deleted the dependabot/maven/auto-value.version-1.10.2 branch July 24, 2023 15:03
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.
0 participants