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.

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

fix(deps): update jdbi3version to v3.40.0 #2588

Merged
merged 1 commit into from
Aug 14, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 12, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
org.jdbi:jdbi3-testcontainers (source) 3.37.1 -> 3.40.0 age adoption passing confidence
org.jdbi:jdbi3-testing (source) 3.37.1 -> 3.40.0 age adoption passing confidence
org.jdbi:jdbi3-sqlobject (source) 3.37.1 -> 3.40.0 age adoption passing confidence
org.jdbi:jdbi3-postgres (source) 3.37.1 -> 3.40.0 age adoption passing confidence
org.jdbi:jdbi3-jackson2 (source) 3.37.1 -> 3.40.0 age adoption passing confidence
org.jdbi:jdbi3-core (source) 3.37.1 -> 3.40.0 age adoption passing confidence

Release Notes

jdbi/jdbi (org.jdbi:jdbi3-testcontainers)

v3.40.0

  • add extension point to decorate withHandle and friends (#​2448)
    • fix PreparedBatch c'tor problem where the binding context was not set correctly. (#​2404)
    • Slight memory optimization on RowMappers and ColumnMappers findFor (#​2418)
    • JsonMapper implementations now bind the Type earlier, which saves work in Jackson and Gson (#​2420)
    • performance improvements for all ExtensionConfigurer implementations (#​2416, #​2424)
    • Remove JSR 305 annotations from the Jdbi codebase, one small step closer to JPMS. (#​2408)
    • remove unnecessary tests before adding standard methods to extension objects (#​2414)
    • Update h2 to 2.2.220 (#​2428)
    • various small performance improvements (#​2436, #​2437, #​2440)
    • improve generator performance (#​2439)

v3.39.1

3.39.x is the last release of Jdbi to support Java 8. Java 8 is
obsolete for a long time and the burden of supporting it in Jdbi has
grown as parts of our tool chain and libraries no longer support
it. We intend to do occasional bug patches for significant bugs or
security issues but there will be no further active development
work.

  • add Extensions#failFast() to enable extension objects with misconfigured methods to fail at first access. Default is to fail when a misconfigured method is accessed for the first time.

  • add new @RegisterCollector customizing annotation (#​2377)

  • correctly return null for OutParameters when the called procedure returns NULL.

  • promoted from @Beta to stable (no functional changes, some minor doc reformatting and additions)

    • JdbiProperty, DatabaseValue, PropagateNull, GenerateSqlObject annotations
    • NamedArgumentFinder, SetObjectArgumentFactory, GetObjectColumnMapperFactory, GenericMapMapperFactory, RowViewMapper
    • MapMappers configuration object
    • ConfigCache functionality
    • SqlStatementCustomizer#warm() and SqlStatementParameterCustomizer#warm()
    • template engines
    • moshi json support
  • promoted from @Alpha to @Beta (no functional changes, doc cleanups)

    • Codec functionality
    • BaseStatement#attachToHandleForCleanup()
    • PostGIS support

v3.39.0

  • don't use. Functional equivalent to 3.39.1 but missing some tests and the Alpha/Beta promotions. Prefer 3.39.1

v3.38.3

  • allow unknown result mappers during ResultReturner warmup. This restores the pre-3.38.0 behavior
    where SQLObject classes with invalid methods could be used unless a method is explicitly called (#​2342)
    • document vavr incompatibility between 0.10.x and 1.0.0-alpha (#​2350)
    • Handle.inTransaction: improve exception thrown when restoring transaction isolation #​2343
    • add support for Guice 6.x (using javax.inject annotations) and guice 7.x (using jakarta.inject annotations)

v3.38.2

  • spring5 JdbiUtil: fix thread safety #​2341

v3.38.1

  • Dramatic performance improvement around copying configuration objects when creating statements
    Should reduce allocation rate and time spent in ConcurrentHashMap init

v3.38.0

  • CaseStrategy is now an official API (dropped @​Beta) (#​2309)
    • rewrite AccessibleObjectStrategy into an enum (#​2310)
    • allow user defined functions for message rendering (#​2311)
    • fix GenericType creation in parameterized classes (#​2305)
    • add SqlStatements#setAttachAllStatementsForCleanup. Setting this configuration flag will attach all created statements to their handles for resource cleanup. Default is false. (#​2293, thanks @​jodastephen)
    • add SqlStatements#setAttachCallbackStatementsForCleanup. Setting this configuration flag will attach all created statements within one of the Jdbi callback methods to the handle. This allows code that uses the Jdbi callback methods to delegate resource management fully to Jdbi. This flag is set by default. (#​2293, thanks @​jodastephen)
    • fix problem when using the jdbi bom in spring projects (#​2295, thanks @​jedvardsson)
    • add JdbiExecutor for async Jdbi operations (#​2280, thanks @​leblonk)
    • rewrite the core extension framework, move functionality from sqlobject to core
    • rewrite sqlobject and the generator to use the new extension framework, deprecate functionality that moved to the core
    • StringTemplate engine: handle st4 errors rather than logging to stderr. Allow configuring missing attribute as a fatal error
    • StringTemplate 4.3.4
    • update spring framework dependency to 5.3.27 (address CVE-2023-20861, CVE-2023-20863)
    • ResultIterable methods: set(), collectToMap(), toCollection(), collectInto(), collectIntoList(), collectIntoSet()
    • Helpers to make registering CollectorFactory easier
    • FreemarkerEngine encourages singleton use so caching works better
    • Support Consumer<Iterable> as a consumer argument for operations that return multiple results.

Configuration

📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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


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

This PR has been generated by Mend Renovate. View repository job log here.

@boring-cyborg boring-cyborg bot added the api API layer changes label Aug 12, 2023
@codecov
Copy link

codecov bot commented Aug 12, 2023

Codecov Report

Merging #2588 (0f532a7) into main (79139c9) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #2588   +/-   ##
=========================================
  Coverage     83.28%   83.28%           
  Complexity     1287     1287           
=========================================
  Files           243      243           
  Lines          5936     5936           
  Branches        279      279           
=========================================
  Hits           4944     4944           
  Misses          845      845           
  Partials        147      147           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@renovate renovate bot force-pushed the renovate/jdbi3version branch 3 times, most recently from ac0c111 to 01a17ed Compare August 14, 2023 16:38
@renovate renovate bot changed the title fix(deps): update jdbi3version to v3.40.0 (minor) fix(deps): update jdbi3version to v3.40.0 Aug 14, 2023
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@wslulciuc wslulciuc merged commit 1a068de into main Aug 14, 2023
13 checks passed
@wslulciuc wslulciuc deleted the renovate/jdbi3version branch August 14, 2023 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api API layer changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant