Skip to content

Releases: JetBrains/amper

0.5.0

05 Nov 13:28
Compare
Choose a tag to compare

Full Changelog: v0.4.0...v0.5.0

See our release blog post for the highlights, and to learn about the tooling improvements.

Breaking changes

  • AMPER-658 — Update the default Kotlin language version to 2.0
  • AMPER-3449 — Update Kotlin to 2.0.21
  • AMPER-3300 — Update kotlinx.serialization built-in version to 1.7.3

New features

  • AMPER-532 — Support composeResources in standalone Amper
  • AMPER-583 — Add ./amper update command to update Amper scripts
  • AMPER-891 — Support Android application signing
  • AMPER-959 — Support KSP (Kotlin Symbol Processing) in standalone Amper
  • AMPER-3304 — Support kotlin-parcelize compiler plugin

Enhancements

  • AMPER-247 — Support versionCode and versionName for Android
  • AMPER-807 — Support Kotlin tests for iOS modules and fragments in standalone Amper
  • AMPER-813 — Remove android:maxSdkVersion
  • AMPER-2288 — Support BOM defined in metadata of external dependencies
  • AMPER-2331 — Support Android API level 35
  • AMPER-2828 — Add kotlin-reflect to built-in catalog
  • AMPER-3301 — Support importing shared iOS library modules into swift code
  • AMPER-3325 — Add settings.kotlin.serialization.version to allow users to control it
  • AMPER-3417 — Add built-in catalog for kotlinx.serialization core and formats
  • AMPER-3455 — Use a JRE (JBR) in amper wrapper scripts instead of a JDK

Usability improvements / cosmetics

  • AMPER-585 — amper.sh should be able to run in parallel for the first time
  • AMPER-587 — amper run should support input from stdin / interactive
  • AMPER-597 — Missing/incorrect template file should results in a build error
  • AMPER-599 — IDE and CLI should emit a warning if a template file named incorrectly
  • AMPER-779 — Amper should report incorrect/unknown configuration keys
  • AMPER-885 — "No catalog value for key" error for $compose could be clearer
  • AMPER-967 — The 'Product type definition is missing' error should mention the problematic module name
  • AMPER-2825 — Non user-friendly stacktrace when main class/fun is missing
  • AMPER-3422 — Improve parsing resilience for Compose related errors
  • AMPER-3636 — Dependencies on local modules with invalid paths lead to weird error
  • AMPER-3737 — Empty compose version set leads to non-comprehensible error output
  • AMPER-974 — "> IDLE" marks do not erase the previously running task

Bug fixes

  • AMPER-462 — `buildFragmentSeeds()` generates seeds with undeclared platforms
  • AMPER-691 — Multiplatform Amper Fleet project: actual implementation cannot be shared code in aliased source set
  • AMPER-795 — Guava is not resolved after import
  • AMPER-879 — Codegen custom tasks are incompatible with language version 2.0
  • AMPER-918 — Dependencies of leaf-platform module are not resolved correctly in Ide if some subset of leaf platforms is specified for a module only
  • AMPER-929 — Specifying a dependency in an invalid format throws instead of proper error reporting
  • AMPER-936 — Android App Fails to Launch via Fleet Due to Incorrect APK Name
  • AMPER-943 — project.yaml globs don't match correctly with /./ or /../
  • AMPER-945 — Regression: custom JUnit platform engine is not picked up by standalone Amper
  • AMPER-958 — Gradle import successful, but dependencies are not updated
  • AMPER-972 — File was returned from dependency resolution, but is missing on disk
  • AMPER-975 — Jaeger server is not stopped when stopping Amper
  • AMPER-1043 — Incremental cache for dependency resolution is broken
  • AMPER-2290 — Problems with kotlinx.serialization 1.7.2
  • AMPER-2334 — Android fragment in KMP library doesn't see Android platform's declarations
  • AMPER-2806 — Unable to parse pom file MissingFieldException for JavaFX dependency
  • AMPER-2808 — Dependencies declared in pom.xml with scope=test should be ignored
  • AMPER-3287 — Processes launched by Amper might leak if the CLI is stopped with Ctrl+C
  • AMPER-3291 — Unify local artifacts storages used by DR for CLI and for Ide sync.
  • AMPER-3292 — java.lang.IllegalStateException: No value
  • AMPER-3294 — Fail...
Read more

0.4.0

08 Aug 07:23
Compare
Choose a tag to compare

Full Changelog: v0.3.0...v0.4.0

See our release blog post for the highlights, and to learn about the tooling improvements.

Breaking changes

  • AMPER-760 Amper is now published to a new Maven repository.
    This affects the Gradle plugin, as well as the standalone Amper distribution and executables:

    • Old repository URL: https://maven.pkg.jetbrains.space/public/p/amper/amper
    • New repository URL: https://packages.jetbrains.team/maven/p/amper/amper

    See Usage.md for instructions on how to update your project.

  • AMPER-393 Amper modules are no longer automatically discovered by searching the whole file system hierarchy.
    The documentation has been updated accordingly.

    • In Gradle-based Amper projects, modules with a module.yaml file now need to be listed alongside other Gradle modules in settings.gradle(.kts)
    • In multi-module projects using standalone Amper, a project.yaml file is now required and must list the modules to include in the project. Nothing changes for single-module projects.

Enhancements

  • AMPER-685 User-friendly error message when a task doesn't exist
  • AMPER-717 Fail fast if the Android SDK license isn't accepted
  • AMPER-790 Inspection about incompatible settings or settings under an incorrect section

Bug fixes

  • AMPER-494 'buildSrc' cannot be used as a project name as it is a reserved name
  • AMPER-624 Compilation fails with language version 2.0
  • AMPER-689 Fail to resolve kotlin-test-annotations-common in a multiplatform context
  • AMPER-836 Support repositories basic authentication in DR
  • AMPER-910 'Redundant setting' inspection false positive

v0.3.1

06 Jun 13:00
Compare
Choose a tag to compare

Full Changelog: v0.3.0...v0.3.1

Main changes:

  • AMPER-625 Update Kotlin to 2.0 release
  • AMPER-628 Update Compose to 1.6.10 release
  • AMPER-620 Update Apple Gradle plugin to include the latest fixes (222.4595-0.23.2)
  • AMPER-443 Compose doesn't work with Gradle 8.6+
  • Support Gradle > 8.6 for the bundled Compose version (and improve error message for other versions).

v0.3.0

28 May 08:34
Compare
Choose a tag to compare

Full Changelog: v0.2.2...v0.3.0

See our release blog post for the highlights, and to
learn about the tooling improvements.

  • Standalone version of Amper. See the usage instructions.
    • Build, test, and run JVM and Android applications in CLI and Fleet.
    • iOS support is on the way.
    • Standalone Amper can automatically download and configure the build environment, such as JDK, Android SDK.
  • Gradle-based Amper has been updated with the following plugins:
    • Kotlin 2.0.0-RC3
    • Compose 1.6.10-rc01
    • Android 8.2
  • Gradle 8.6 is recommended for the Gradle-based Amper. Gradle 8.7+ is not yet supported.
  • Support the Wasm platform for libraries.

Breaking changes

Amper now uses the release javac option instead of target and source to compile the Java code.
This version is also passed to the Kotlin compiler on the JVM platform.

You need to update your configuration files. If you have the following settings:

settings:
  java:
    source: 17
  jvm:
    target: 17

Remove java:source: and change jvm:target: to jvm:release::

settings:
  jvm:
    release: 17

See the DSL reference for details.

v0.2.2

28 May 08:34
Compare
Choose a tag to compare

Full Changelog: v0.2.0...v0.2.2

v0.2.0

28 May 08:33
Compare
Choose a tag to compare
docs: mention AABs and IPA in publishing

(cherry picked from commit e5de94093f7da11f96a5a0b0e1addf99b999b7a6)

v0.1.4

28 May 08:33
Compare
Choose a tag to compare
Update a plugin version to 0.1.4

v0.1.3

28 May 08:33
Compare
Choose a tag to compare
Update plugin version to 0.1.3

v0.1.2

28 May 08:32
Compare
Choose a tag to compare
Update plugin version to 0.1.2

v0.1.1

28 May 08:32
Compare
Choose a tag to compare
0.1.1