github kestra-io/kestra v0.15.0
on GitHub

latest releases: v0.17.20, v0.18.8, v0.15.22...
6 months ago

Features

Bug Fixes

Documentation

Code Refactoring

Chores

Commits

  • c7640c8: Update README.md (#2933) (Scott Gunn) #2933
  • ea52d21: fix(cli,core): simplify KestraAplicationContextBuilder (Loïc Mathieu) #2750
  • bedb22b: feat(webserver,cli): replace our custom access log by Micronaut's one (Loïc Mathieu) #2750
  • 7b52ef4: fix(cli,core): disable for now tests that needs plugin recompilation (Loïc Mathieu) #2750
  • feature(core): relative time filter #2894 (yuri1969)
  • 7af71aa: Feat(core, jdbc): refactor execution loggind and add the tenant (Loïc Mathieu) #3071
  • 0514962: Feat/schedule refacto (#3075) (Loïc Mathieu) #3075
  • ffc8800: fix(ui, websever): rename startDateRange to timeRange and add support for it in the mass actions (Loïc Mathieu) #3099
  • ff725e1: feat/setup-configuration (#3025) (brian-mulier-p) #3025
  • 6740aa2: closes #3111 (Anna Geller)

Breaking Changes

  • Migration to Micronaut 4: Kestra 0.15.0 migrates to Micronaut 4.3. This migration brings a lot of improvements and new features, but it also introduces some breaking changes. Check the migration guide for more details on how you can migrate your custom plugins.
  • Change in concurrency control with the Kafka runner: if you're on the Kestra Enterprise Edition with a Kafka backend, make sure that all executions that use concurrency limits terminate (they must finish or you need to manually kill them) before upgrading to 0.15.0. This is due to a fix implementing concurrency limits without ExecutionQueued. To efficiently drain all your executions, you can stop the Webserver and the Scheduler, and then wait for the Executor and the Worker to finish pending executions. Once all executions are finished, you can upgrade to 0.15.0.
  • Backfill change: Deprecation of backfill source code property in the Schedule trigger in favor of the new UI backfill feature. You can still have backfills specified in the source code but they will have no effect, as backfill is now an API-first feature.
  • Inputs now use id instead of name: the name property is deprecated in favor of id for consistency with the rest of the Kestra flow configuration, including the flows, tasks, and triggers. This deprecation is implemented in a non-breaking way so that you don't need to immediately change your existing flows in order to successfully migrate to 0.15.0, but we recommend using the id property at least for new flows. The name property will be removed in the future.
  • Subflow outputs behavior: the outputs property of a Subflow task is deprecated. Instead, use flow outputs to pass data between flows. If you have many subflows passing data between each other and you need more time for the migration, you can add a configuration to keep the old behavior. Check the migration documentation for more details.
  • scheduleConditions deprecation: to make the configuration more consistent, we've unified the scheduleConditions with the generic trigger conditions. As a result of this change, the scheduleConditions property is marked as deprecated; simply rename it to conditions to future-proof your flows. This change is implemented in a non-breaking way, so you don't need to immediately change your existing flows in order to successfully migrate to 0.15.0. However, we recommend using the conditions property at least for new flows. The scheduleConditions property will be removed in the future. For more details and examples, check the Schedule Conditions migration guide.
Check out latest releases or
releases around kestra-io/kestra v0.15.0

Don't miss a new kestra release

NewReleases is sending notifications on new releases.

Get notifications