Bump jvm from 1.6.21 to 1.7.21

[dependabot[bot]]

Bumps jvm from 1.6.21 to 1.7.21.

Release notes

Sourced from jvm's releases.

Kotlin 1.7.21

Changelog

Compiler

• KT-54463 Delegating to a field with a platform type causes java.lang.NoSuchFieldError: value$delegate
• KT-54509 Ir Interpreter: unable to evaluate string concatenation with "this" as argument
• KT-54004 Builder type inference does not work correctly with variable assignment and breaks run-time
• KT-54393 Change in behavior from 1.7.10 to 1.7.20 for java field override.
• KT-54615 JVM: Internal error in file lowering: java.lang.AssertionError: Error occurred while optimizing an expression
• KT-54581 JVM: "VerifyError: Bad type on operand stack" with generic inline function and when inside try-catch block
• KT-53146 JVM IR: unnecessary checkcast of null leads to NoClassDefFoundError if the type isn't available at runtime
• KT-54600 NPE on passing nullable Kotlin lambda as Java's generic SAM interface with super type bound
• KT-54707 "VerifyError: Bad type on operand stack" in inline call chain on a nullable array value
• KT-54650 Binary incompatible ABI change in Kotlin 1.7.20
• KT-54802 "VerifyError: Bad type on operand stack" for inline functions on arrays

Native. Runtime. Memory

• KT-54498 Deprecation message of 'FreezingIsDeprecated' is not really helpful

Tools. Gradle. Multiplatform

• KT-54387 Remove MPP alpha stability warning
• KT-48436 False positive "The Kotlin source set androidAndroidTestRelease was configured but not added to any Kotlin compilation"

Tools. JPS

• KT-45474 False positive NO_ELSE_IN_WHEN on sealed class with incremental compilation

Checksums

File	Sha256
kotlin-compiler-1.7.21.zip	8412b31b808755f0c0d336dbb8c8443fa239bf32ddb3cdb81b305b25f0ad279e
kotlin-native-linux-x86_64-1.7.21.tar.gz	0f9eb04a5ee0665a195c1f1093c778f5696216660feb638b29f923f586093dd0
kotlin-native-macos-x86_64-1.7.21.tar.gz	9530cadcf05cfd6111ef35725115009283b1a0292427261b78d43853c35ccd44
kotlin-native-macos-aarch64-1.7.21.tar.gz	f75e1a68e193b0cd9df56f15166fb4e721641b408065531b620cf204d78922e5
kotlin-native-windows-x86_64-1.7.21.zip	5e76301f6c386ea83dc668e171887244908c18da636f7237d5371b56d8fec8da

Kotlin 1.7.20

1.7.20

Analysis API

• KT-52667 FIR IDE: fun interfaces (SAM interfaces) are not properly resolved
• KT-52136 FIR: Implicit type declaration from the other module cannot be used for overloading

Analysis API. FE1.0

... (truncated)

Changelog

Sourced from jvm's changelog.

1.7.21

Compiler

• KT-54463 Delegating to a field with a platform type causes java.lang.NoSuchFieldError: value$delegate
• KT-54509 Ir Interpreter: unable to evaluate string concatenation with "this" as argument
• KT-54004 Builder type inference does not work correctly with variable assignment and breaks run-time
• KT-54393 Change in behavior from 1.7.10 to 1.7.20 for java field override.
• KT-54615 JVM: Internal error in file lowering: java.lang.AssertionError: Error occurred while optimizing an expression
• KT-54581 JVM: "VerifyError: Bad type on operand stack" with generic inline function and when inside try-catch block
• KT-53146 JVM IR: unnecessary checkcast of null leads to NoClassDefFoundError if the type isn't available at runtime
• KT-54600 NPE on passing nullable Kotlin lambda as Java's generic SAM interface with super type bound
• KT-54707 "VerifyError: Bad type on operand stack" in inline call chain on a nullable array value
• KT-54650 Binary incompatible ABI change in Kotlin 1.7.20
• KT-54802 "VerifyError: Bad type on operand stack" for inline functions on arrays

Native. Runtime. Memory

• KT-54498 Deprecation message of 'FreezingIsDeprecated' is not really helpful

Tools. Gradle. Multiplatform

• KT-54387 Remove MPP alpha stability warning
• KT-48436 False positive "The Kotlin source set androidAndroidTestRelease was configured but not added to any Kotlin compilation"

Tools. JPS

• KT-45474 False positive NO_ELSE_IN_WHEN on sealed class with incremental compilation

1.7.20

Analysis API

• KT-52667 FIR IDE: fun interfaces (SAM interfaces) are not properly resolved
• KT-52136 FIR: Implicit type declaration from the other module cannot be used for overloading

Analysis API. FE1.0

• KT-51962 Analysis API: Finish Analysis API for FE1.0

Analysis API. FIR

• KT-52779 FIR IDE: Import Optimizer cannot handle generic type qualifiers
• KT-50236 Fix OOB modification trackers for non-Kotlin code
• KT-51240 Analysis API: KtAnalysisSession for a specific module cannot create a symbol for PSI that cannot be seen from that module.
• KT-50868 Analysis API: decompiled type aliases are not resolved

Compiler

... (truncated)

Commits

• e7f77e9 Keep track of array types in OptimizationBasicInterpreter
• 7deaab9 Edit changelog for 1.7.21
• 0b49dc2 Fix binary compatibility for inlined local delegated properies
• 90b3e21 Advance bootstrap to 1.7.21
• c55a197 Edit changelog for 1.7.21
• b1b18c2 Add regression test for KT-54707
• 7a25213 KT-53465, KT-53677 Get rid of unnecessary checkcasts to array of reified type
• 2587f3e Edit changelog for 1.7.21
• 62dfe43 Add changelog for 1.7.21
• 34ae02b K1: add more tests for BI assignment checker, fix corner cases
• 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)

[pull-request-quantifier-deprecated[bot]]

This PR has 2 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 : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .kts : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

[dependabot[bot]]

Looks like jvm is up-to-date now, so this is no longer needed.