build(deps): bump jvm from 1.9.21 to 1.9.23

[dependabot]

Bumps jvm from 1.9.21 to 1.9.23.

Release notes

Sourced from jvm's releases.

Kotlin 1.9.23

1.9.23

Apple Ecosystem

• KT-65542 Cinterop tasks fails if Xcode 15.3 is used

Backend. Wasm

• KT-64486 Kotlin/Wasm/WASI exported function callback for coroutines support

Compiler

• KT-53478 Could not load module
• KT-66044 JDK's new API is used over Kotlin's SDK functions
• KT-64640 Prevent mutating SequenceCollection methods from JDK 21 be available on read-only collections
• KT-65441 K1: Remove JDK 21 getFirst()/getLast() in (Mutable)List interfaces
• KT-65634 K/N: data race during monolithic cache creation
• KT-53109 CompilationErrorException generateUnboundSymbolsAsDependencies with builder inference and lambdas
• KT-52757 Type inference for builders fails if inferred from a function

Tools. Gradle

• KT-65792 Add JSON build report
• KT-65091 Update compiler metrics in build reports
• KT-62490 KGP dropping resource directories

Tools. Gradle. JS

• KT-64119 K/JS: Migrate package manager from Yarn onto NPM
• KT-64561 K/JS tests are not executed after upgrade to 1.9.22

Tools. Gradle. Multiplatform

• KT-65954 commonTest dependencies affect commoMainMetadata compilation

Tools. Gradle. Native

• KT-64573 Default value for produceUnpackedKlib was not provided

Kotlin 1.9.22

Changelog

JavaScript

• KT-63719 KJS: Test results ignored for ES module kind
• KT-63808 compileTestDevelopmentExecutableKotlinJs failed in JsIntrinsicTransformers

Native

... (truncated)

Changelog

Sourced from jvm's changelog.

1.9.23

Apple Ecosystem

• KT-65542 Cinterop tasks fails if Xcode 15.3 is used

Backend. Wasm

• KT-64486 Kotlin/Wasm/WASI exported function callback for coroutines support

Compiler

• KT-53478 Could not load module
• KT-66044 JDK's new API is used over Kotlin's SDK functions
• KT-64640 Prevent mutating SequenceCollection methods from JDK 21 be available on read-only collections
• KT-65441 K1: Remove JDK 21 getFirst()/getLast() in (Mutable)List interfaces
• KT-65634 K/N: data race during monolithic cache creation
• KT-53109 CompilationErrorException generateUnboundSymbolsAsDependencies with builder inference and lambdas
• KT-52757 Type inference for builders fails if inferred from a function

Tools. Gradle

• KT-65792 Add JSON build report
• KT-65091 Update compiler metrics in build reports
• KT-62490 KGP dropping resource directories

Tools. Gradle. JS

• KT-64119 K/JS: Migrate package manager from Yarn onto NPM
• KT-64561 K/JS tests are not executed after upgrade to 1.9.22

Tools. Gradle. Multiplatform

• KT-65954 commonTest dependencies affect commoMainMetadata compilation

Tools. Gradle. Native

• KT-64573 Default value for produceUnpackedKlib was not provided

1.9.22

JavaScript

• KT-63719 KJS: Test results ignored for ES module kind
• KT-63808 compileTestDevelopmentExecutableKotlinJs failed in JsIntrinsicTransformers

Native

• KT-64139 Weird bug with while and coroutine in Kotlin Native

... (truncated)

Commits

• 4c571ac Edit changelog for 1.9.23
• 1ca6f32 Revert "[Wasm] Implement IrLinkageError end enable partial linker"
• 3b90682 Add changelog for 1.9.23
• f327391 Add validation for empty kotlin.build.report.json.directory property
• 2f19d2e Add JSON output type for build reports
• 666a2f2 [Wasm] Implement IrLinkageError end enable partial linker
• 4dc6689 [Native] Support Xcode 15.3 — add back the TargetConditional.h macros
• d3b2c6f K1: change depr. level of List.getFirst to HIDDEN but don't force it on overr...
• c041815 K1/K2: add tests for KT-65441 current behavior
• c262b97 K1: introduce BUILDER_INFERENCE_STUB_PARAMETER_TYPE to prevent compiler crashes
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pull-request-quantifier-deprecated]

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +2 -2
Percentile : 1.6%

Total files changed: 2

Change summary by file extension:
.kts : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.