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 dagger from 2.40.5 to 2.41 #5980

Merged
merged 1 commit into from
May 9, 2022
Merged

Bump dagger from 2.40.5 to 2.41 #5980

merged 1 commit into from
May 9, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 9, 2022

Bumps dagger from 2.40.5 to 2.41.
Updates hilt-android-gradle-plugin from 2.40.5 to 2.41

Release notes

Sourced from hilt-android-gradle-plugin's releases.

Dagger 2.41

What’s New In Dagger

Potentially Breaking Changes

  • This release fixes a recently noticed, but long-standing bug (#3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e. it is not on the classpath).

    Dagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. While Dagger does its best to avoid failing the build for non-scope/qualifier annotations, in general it’s not possible to tell if an annotation is a scope/qualifier unless its type is resolvable -- thus, Dagger may fail on non-scope/qualifier annotations as well.

    If these changes break your build, we recommend first trying to fix the breakage by adding the appropriate missing dependencies to your build (in most cases the error message should tell you exactly what type is missing). Although not recommended, you can revert back to the old behavior using the compiler option -Adagger.strictSuperficialValidation=DISABLED; however, this option will be removed in a future release. If the breakage is specifically due to the validation of transitive component dependencies, you may choose to disable that validation using -Adagger.validateTransitiveComponentDependencies=DISABLED. If the breakage is specifically due to androidx.hilt:hilt-lifecycle-viewmodel you will need to migrate to the native Hilt API (see google/dagger#3257).

  • This release fixes an accidental regression (introduced in Dagger version 2.39) that allowed requesting a raw @Inject constructor type which was previously not allowed (a61aa50c8).

    We expect breakages due to this issue to be relatively rare and easy to fix -- just replace the raw type with the proper parameterized type.

  • The string format of bindings has changed slightly (just spacing). SPI plugins that depend on this format may break. Note that as KSP migrations go forward, other string formats may change slightly in similar ways as well.

New Changes

  • Dagger error messages for unresolvable deferred types have been improved. Error messages now tell you exactly which type could not be resolved and where it was found. Fixes #​​2208 (727068f38), Fixes #3133 (78646fbe6)

  • Dagger now supports reading the jakarta.inject versions of Inject, Scope, Qualifier, and Singleton. Dagger currently does not support jakarta.inject.Provider. Also, code generated by Dagger (and Hilt) continue to use the javax.inject symbols. Further changes and support to come in future releases. (219551376)

Bug Fixes

  • Updates dagger-lint to avoid displaying a warning due to missing Vendor information. (cb33cc584)
  • Fixes an issue where Dagger's lint checks wouldn't work with lint 30.2.x-alpha due to using a removed API. (33ba899f9)
  • Fix #3069 where a class named "Create" could cause a conflict with the create() method on a component. (5ba04fb38)
  • Fix #3143 where a crash about a missing shard would occur when a members injection binding exists in a parent component. (3545f0193)
  • Fix #3091. Update MapKey error message to reference new auto-value artifacts. (91e7df18e)

What’s New In Hilt

New Changes

Bug Fixes

  • Fix an issue where Hilt transform was not correctly updating the Signature attribute of an @AndroidEntryPoint whose superclass contained a type variable. (475cc0516)
  • Fixes #3119: Added kotlin-stdlib to pom dependencies to avoid breaking java-only projects. (3ec422e78)
  • Support AGP 7.2 ASM API changes (5502cd770)
Commits
  • 085460c 2.41 release
  • 0b9398e Add Gradle tests that use transitive types and annotation on base components,...
  • 3ae46b8 Internal changes.
  • 703ccc8 Migrate CompilerOption to use XProcessing.
  • c295d12 [Dagger Cleanup]: Remove unused code.
  • 6758662 Migrate MethodSignatureFormatter to XProcessing.
  • 0f373eb Migrate ValidationReport to XProcessing.
  • 97f94d2 Perform superficial validation before getting annotation values from componen...
  • 4da72ca Improve coverage of existing Gradle tests.
  • a8b35a1 Add transitive component dependencies test to our Gradle test.
  • Additional commits viewable in compare view

Updates dagger from 2.40.5 to 2.41

Release notes

Sourced from dagger's releases.

Dagger 2.41

What’s New In Dagger

Potentially Breaking Changes

  • This release fixes a recently noticed, but long-standing bug (#3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e. it is not on the classpath).

    Dagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. While Dagger does its best to avoid failing the build for non-scope/qualifier annotations, in general it’s not possible to tell if an annotation is a scope/qualifier unless its type is resolvable -- thus, Dagger may fail on non-scope/qualifier annotations as well.

    If these changes break your build, we recommend first trying to fix the breakage by adding the appropriate missing dependencies to your build (in most cases the error message should tell you exactly what type is missing). Although not recommended, you can revert back to the old behavior using the compiler option -Adagger.strictSuperficialValidation=DISABLED; however, this option will be removed in a future release. If the breakage is specifically due to the validation of transitive component dependencies, you may choose to disable that validation using -Adagger.validateTransitiveComponentDependencies=DISABLED. If the breakage is specifically due to androidx.hilt:hilt-lifecycle-viewmodel you will need to migrate to the native Hilt API (see google/dagger#3257).

  • This release fixes an accidental regression (introduced in Dagger version 2.39) that allowed requesting a raw @Inject constructor type which was previously not allowed (a61aa50c8).

    We expect breakages due to this issue to be relatively rare and easy to fix -- just replace the raw type with the proper parameterized type.

  • The string format of bindings has changed slightly (just spacing). SPI plugins that depend on this format may break. Note that as KSP migrations go forward, other string formats may change slightly in similar ways as well.

New Changes

  • Dagger error messages for unresolvable deferred types have been improved. Error messages now tell you exactly which type could not be resolved and where it was found. Fixes #​​2208 (727068f38), Fixes #3133 (78646fbe6)

  • Dagger now supports reading the jakarta.inject versions of Inject, Scope, Qualifier, and Singleton. Dagger currently does not support jakarta.inject.Provider. Also, code generated by Dagger (and Hilt) continue to use the javax.inject symbols. Further changes and support to come in future releases. (219551376)

Bug Fixes

  • Updates dagger-lint to avoid displaying a warning due to missing Vendor information. (cb33cc584)
  • Fixes an issue where Dagger's lint checks wouldn't work with lint 30.2.x-alpha due to using a removed API. (33ba899f9)
  • Fix #3069 where a class named "Create" could cause a conflict with the create() method on a component. (5ba04fb38)
  • Fix #3143 where a crash about a missing shard would occur when a members injection binding exists in a parent component. (3545f0193)
  • Fix #3091. Update MapKey error message to reference new auto-value artifacts. (91e7df18e)

What’s New In Hilt

New Changes

Bug Fixes

  • Fix an issue where Hilt transform was not correctly updating the Signature attribute of an @AndroidEntryPoint whose superclass contained a type variable. (475cc0516)
  • Fixes #3119: Added kotlin-stdlib to pom dependencies to avoid breaking java-only projects. (3ec422e78)
  • Support AGP 7.2 ASM API changes (5502cd770)
Commits
  • 085460c 2.41 release
  • 0b9398e Add Gradle tests that use transitive types and annotation on base components,...
  • 3ae46b8 Internal changes.
  • 703ccc8 Migrate CompilerOption to use XProcessing.
  • c295d12 [Dagger Cleanup]: Remove unused code.
  • 6758662 Migrate MethodSignatureFormatter to XProcessing.
  • 0f373eb Migrate ValidationReport to XProcessing.
  • 97f94d2 Perform superficial validation before getting annotation values from componen...
  • 4da72ca Improve coverage of existing Gradle tests.
  • a8b35a1 Add transitive component dependencies test to our Gradle test.
  • Additional commits viewable in compare view

Updates dagger-compiler from 2.40.5 to 2.41

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.41

What’s New In Dagger

Potentially Breaking Changes

  • This release fixes a recently noticed, but long-standing bug (#3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e. it is not on the classpath).

    Dagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. While Dagger does its best to avoid failing the build for non-scope/qualifier annotations, in general it’s not possible to tell if an annotation is a scope/qualifier unless its type is resolvable -- thus, Dagger may fail on non-scope/qualifier annotations as well.

    If these changes break your build, we recommend first trying to fix the breakage by adding the appropriate missing dependencies to your build (in most cases the error message should tell you exactly what type is missing). Although not recommended, you can revert back to the old behavior using the compiler option -Adagger.strictSuperficialValidation=DISABLED; however, this option will be removed in a future release. If the breakage is specifically due to the validation of transitive component dependencies, you may choose to disable that validation using -Adagger.validateTransitiveComponentDependencies=DISABLED. If the breakage is specifically due to androidx.hilt:hilt-lifecycle-viewmodel you will need to migrate to the native Hilt API (see google/dagger#3257).

  • This release fixes an accidental regression (introduced in Dagger version 2.39) that allowed requesting a raw @Inject constructor type which was previously not allowed (a61aa50c8).

    We expect breakages due to this issue to be relatively rare and easy to fix -- just replace the raw type with the proper parameterized type.

  • The string format of bindings has changed slightly (just spacing). SPI plugins that depend on this format may break. Note that as KSP migrations go forward, other string formats may change slightly in similar ways as well.

New Changes

  • Dagger error messages for unresolvable deferred types have been improved. Error messages now tell you exactly which type could not be resolved and where it was found. Fixes #​​2208 (727068f38), Fixes #3133 (78646fbe6)

  • Dagger now supports reading the jakarta.inject versions of Inject, Scope, Qualifier, and Singleton. Dagger currently does not support jakarta.inject.Provider. Also, code generated by Dagger (and Hilt) continue to use the javax.inject symbols. Further changes and support to come in future releases. (219551376)

Bug Fixes

  • Updates dagger-lint to avoid displaying a warning due to missing Vendor information. (cb33cc584)
  • Fixes an issue where Dagger's lint checks wouldn't work with lint 30.2.x-alpha due to using a removed API. (33ba899f9)
  • Fix #3069 where a class named "Create" could cause a conflict with the create() method on a component. (5ba04fb38)
  • Fix #3143 where a crash about a missing shard would occur when a members injection binding exists in a parent component. (3545f0193)
  • Fix #3091. Update MapKey error message to reference new auto-value artifacts. (91e7df18e)

What’s New In Hilt

New Changes

Bug Fixes

  • Fix an issue where Hilt transform was not correctly updating the Signature attribute of an @AndroidEntryPoint whose superclass contained a type variable. (475cc0516)
  • Fixes #3119: Added kotlin-stdlib to pom dependencies to avoid breaking java-only projects. (3ec422e78)
  • Support AGP 7.2 ASM API changes (5502cd770)
Commits
  • 085460c 2.41 release
  • 0b9398e Add Gradle tests that use transitive types and annotation on base components,...
  • 3ae46b8 Internal changes.
  • 703ccc8 Migrate CompilerOption to use XProcessing.
  • c295d12 [Dagger Cleanup]: Remove unused code.
  • 6758662 Migrate MethodSignatureFormatter to XProcessing.
  • 0f373eb Migrate ValidationReport to XProcessing.
  • 97f94d2 Perform superficial validation before getting annotation values from componen...
  • 4da72ca Improve coverage of existing Gradle tests.
  • a8b35a1 Add transitive component dependencies test to our Gradle test.
  • Additional commits viewable in compare view

Updates hilt-android from 2.40.5 to 2.41

Release notes

Sourced from hilt-android's releases.

Dagger 2.41

What’s New In Dagger

Potentially Breaking Changes

  • This release fixes a recently noticed, but long-standing bug (#3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e. it is not on the classpath).

    Dagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. While Dagger does its best to avoid failing the build for non-scope/qualifier annotations, in general it’s not possible to tell if an annotation is a scope/qualifier unless its type is resolvable -- thus, Dagger may fail on non-scope/qualifier annotations as well.

    If these changes break your build, we recommend first trying to fix the breakage by adding the appropriate missing dependencies to your build (in most cases the error message should tell you exactly what type is missing). Although not recommended, you can revert back to the old behavior using the compiler option -Adagger.strictSuperficialValidation=DISABLED; however, this option will be removed in a future release. If the breakage is specifically due to the validation of transitive component dependencies, you may choose to disable that validation using -Adagger.validateTransitiveComponentDependencies=DISABLED. If the breakage is specifically due to androidx.hilt:hilt-lifecycle-viewmodel you will need to migrate to the native Hilt API (see google/dagger#3257).

  • This release fixes an accidental regression (introduced in Dagger version 2.39) that allowed requesting a raw @Inject constructor type which was previously not allowed (a61aa50c8).

    We expect breakages due to this issue to be relatively rare and easy to fix -- just replace the raw type with the proper parameterized type.

  • The string format of bindings has changed slightly (just spacing). SPI plugins that depend on this format may break. Note that as KSP migrations go forward, other string formats may change slightly in similar ways as well.

New Changes

  • Dagger error messages for unresolvable deferred types have been improved. Error messages now tell you exactly which type could not be resolved and where it was found. Fixes #​​2208 (727068f38), Fixes #3133 (78646fbe6)

  • Dagger now supports reading the jakarta.inject versions of Inject, Scope, Qualifier, and Singleton. Dagger currently does not support jakarta.inject.Provider. Also, code generated by Dagger (and Hilt) continue to use the javax.inject symbols. Further changes and support to come in future releases. (219551376)

Bug Fixes

  • Updates dagger-lint to avoid displaying a warning due to missing Vendor information. (cb33cc584)
  • Fixes an issue where Dagger's lint checks wouldn't work with lint 30.2.x-alpha due to using a removed API. (33ba899f9)
  • Fix #3069 where a class named "Create" could cause a conflict with the create() method on a component. (5ba04fb38)
  • Fix #3143 where a crash about a missing shard would occur when a members injection binding exists in a parent component. (3545f0193)
  • Fix #3091. Update MapKey error message to reference new auto-value artifacts. (91e7df18e)

What’s New In Hilt

New Changes

Bug Fixes

  • Fix an issue where Hilt transform was not correctly updating the Signature attribute of an @AndroidEntryPoint whose superclass contained a type variable. (475cc0516)
  • Fixes #3119: Added kotlin-stdlib to pom dependencies to avoid breaking java-only projects. (3ec422e78)
  • Support AGP 7.2 ASM API changes (5502cd770)
Commits
  • 085460c 2.41 release
  • 0b9398e Add Gradle tests that use transitive types and annotation on base components,...
  • 3ae46b8 Internal changes.
  • 703ccc8 Migrate CompilerOption to use XProcessing.
  • c295d12 [Dagger Cleanup]: Remove unused code.
  • 6758662 Migrate MethodSignatureFormatter to XProcessing.
  • 0f373eb Migrate ValidationReport to XProcessing.
  • 97f94d2 Perform superficial validation before getting annotation values from componen...
  • 4da72ca Improve coverage of existing Gradle tests.
  • a8b35a1 Add transitive component dependencies test to our Gradle test.
  • Additional commits viewable in compare view

Updates hilt-compiler from 2.40.5 to 2.41

Release notes

Sourced from hilt-compiler's releases.

Dagger 2.41

What’s New In Dagger

Potentially Breaking Changes

  • This release fixes a recently noticed, but long-standing bug (#3136) where Dagger’s processors may silently miss a scope/qualifier on a binding if the scope/qualifier annotation is unresolvable (i.e. it is not on the classpath).

    Dagger will now prefer to fail the build if there are any unresolvable annotations present where a scope/qualifier is allowed. While Dagger does its best to avoid failing the build for non-scope/qualifier annotations, in general it’s not possible to tell if an annotation is a scope/qualifier unless its type is resolvable -- thus, Dagger may fail on non-scope/qualifier annotations as well.

    If these changes break your build, we recommend first trying to fix the breakage by adding the appropriate missing dependencies to your build (in most cases the error message should tell you exactly what type is missing). Although not recommended, you can revert back to the old behavior using the compiler option -Adagger.strictSuperficialValidation=DISABLED; however, this option will be removed in a future release. If the breakage is specifically due to the validation of transitive component dependencies, you may choose to disable that validation using -Adagger.validateTransitiveComponentDependencies=DISABLED. If the breakage is specifically due to androidx.hilt:hilt-lifecycle-viewmodel you will need to migrate to the native Hilt API (see google/dagger#3257).

  • This release fixes an accidental regression (introduced in Dagger version 2.39) that allowed requesting a raw @Inject constructor type which was previously not allowed (a61aa50c8).

    We expect breakages due to this issue to be relatively rare and easy to fix -- just replace the raw type with the proper parameterized type.

  • The string format of bindings has changed slightly (just spacing). SPI plugins that depend on this format may break. Note that as KSP migrations go forward, other string formats may change slightly in similar ways as well.

New Changes

  • Dagger error messages for unresolvable deferred types have been improved. Error messages now tell you exactly which type could not be resolved and where it was found. Fixes #​​2208 (727068f38), Fixes #3133 (78646fbe6)

  • Dagger now supports reading the jakarta.inject versions of Inject, Scope, Qualifier, and Singleton. Dagger currently does not support jakarta.inject.Provider. Also, code generated by Dagger (and Hilt) continue to use the javax.inject symbols. Further changes and support to come in future releases. (219551376)

Bug Fixes

  • Updates dagger-lint to avoid displaying a warning due to missing Vendor information. (cb33cc584)
  • Fixes an issue where Dagger's lint checks wouldn't work with lint 30.2.x-alpha due to using a removed API. (33ba899f9)
  • Fix #3069 where a class named "Create" could cause a conflict with the create() method on a component. (5ba04fb38)
  • Fix #3143 where a crash about a missing shard would occur when a members injection binding exists in a parent component. (3545f0193)
  • Fix #3091. Update MapKey error message to reference new auto-value artifacts. (91e7df18e)

What’s New In Hilt

New Changes

Bug Fixes

  • Fix an issue where Hilt transform was not correctly updating the Signature attribute of an @AndroidEntryPoint whose superclass contained a type variable. (475cc0516)
  • Fixes #3119: Added kotlin-stdlib to pom dependencies to avoid breaking java-only projects. (3ec422e78)
  • Support AGP 7.2 ASM API changes (5502cd770)
Commits
  • 085460c 2.41 release
  • 0b9398e Add Gradle tests that use transitive types and annotation on base components,...
  • 3ae46b8 Internal changes.
  • 703ccc8 Migrate CompilerOption to use XProcessing.
  • c295d12 [Dagger Cleanup]: Remove unused code.
  • 6758662 Migrate MethodSignatureFormatter to XProcessing.
  • 0f373eb Migrate ValidationReport to XProcessing.
  • 97f94d2 Perform superficial validation before getting annotation values from componen...
  • 4da72ca Improve coverage of existing Gradle tests.
  • a8b35a1 Add transitive component dependencies test to our Gradle test.
  • 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 dagger from 2.40.5 to 2.41
fc62861 
Bumps `dagger` from 2.40.5 to 2.41.

Updates `hilt-android-gradle-plugin` from 2.40.5 to 2.41
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.40.5...dagger-2.41)

Updates `dagger` from 2.40.5 to 2.41
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.40.5...dagger-2.41)

Updates `dagger-compiler` from 2.40.5 to 2.41
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.40.5...dagger-2.41)

Updates `hilt-android` from 2.40.5 to 2.41
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.40.5...dagger-2.41)

Updates `hilt-compiler` from 2.40.5 to 2.41
- [Release notes](https://github.com/google/dagger/releases)
- [Changelog](https://github.com/google/dagger/blob/master/CHANGELOG.md)
- [Commits](google/dagger@dagger-2.40.5...dagger-2.41)

---
updated-dependencies:
- dependency-name: com.google.dagger:hilt-android-gradle-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:dagger
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:dagger-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:hilt-android
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: com.google.dagger:hilt-compiler
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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 May 9, 2022
@dependabot dependabot bot requested review from a team, yostyle and ericdecanini and removed request for a team May 9, 2022 13:23
@bmarty bmarty merged commit 77977a0 into develop May 9, 2022
@bmarty bmarty deleted the dependabot/gradle/dagger-2.41 branch May 9, 2022 14:59
@github-actions
Copy link

github-actions bot commented May 9, 2022

Matrix SDK

Integration Tests Results:

  • [org.matrix.android.sdk.session]
    = passed=8 failures=12 errors=0 skipped=3
  • [org.matrix.android.sdk.account]
    = passed=3 failures=0 errors=0 skipped=2
  • [org.matrix.android.sdk.internal]
    = passed=110 failures=0 errors=0 skipped=38
  • [org.matrix.android.sdk.ordering]
    = passed=16 failures=0 errors=0 skipped=0
  • [org.matrix.android.sdk.PermalinkParserTest]
    = passed=2 failures=0 errors=0 skipped=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bmarty bmarty bmarty approved these changes

@yostyle yostyle Awaiting requested review from yostyle yostyle was automatically assigned from element-hq/element-android-reviewers

@ericdecanini ericdecanini Awaiting requested review from ericdecanini ericdecanini was automatically assigned from element-hq/element-android-reviewers

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
@bmarty