Skip to content

v0.18.19 - binary-breaking changes in core

Compare
Choose a tag to compare
@kubukoz kubukoz released this 18 May 22:04
· 55 commits to series/0.18 since this release
d7afe21

0.18.19 - ⚠️ binary-breaking changes in core

⚠️ WARNING: This release includes binary-breaking changes in the core module. This is indirectly caused by an upstream change in smithy-lang/smithy.

In the vast majority of applications using Smithy4s, it will not cause runtime issues. However, in the unlikely event that you have custom interpreters that query the .breakingChanges field of a Trait hint, or have that field populated by a non-stdlib trait/hint, you'll have to ensure that all the libraries pulled by your application are compiled against smithy4s 0.18.19 or above.

In sbt, you can check what versions of smithy4s are used by your dependencies using the whatDependsOn task.

We apologize for the inconvenience.

Changes

  • smithy4sUpdateLSPConfig: Replace imports with sources to be more in line with idiomatic smithy-build config in #1518 (see #1459)
  • Update smithy: 1.45.0 to 1.49.0 (binary breaking) in #1485
  • Rendered type aliases are now sorted alphabetically in #1523
  • Add handlers construct to facilitate the decoupling of operation implementations in #1522
  • Improve cache in code generation (sbt) by @majk-p in #1499
  • Sort generated type aliases during rendering by @Baccata in #1523

Other changes

New Contributors

Full Changelog: v0.18.18...v0.18.19