Release Update - 9/29/2016

Posted by AureliaEffect on September 29, 2016

This week we've got more improvements and fixes in the core. We've also got some sweet new features for the validation library.


The validation library is almost ready for beta. We're really happy with how it has evolved and are grateful for the amazing feedback and contributions from the community, under the humble leadership of core team member Jeremy Danyow.

Some of the new features are:

  • Add a new changeOrBlur trigger.
  • Enable specifying a validate trigger on individual bindings.
  • Rule prioritization and bailing.


As mentioned above, in addition to the validation feature updates, we continue to make improvements throughout all Aurelia libraries. You can read the detailed list of changes below.

aurelia-path 1.1.1 (2016-09-23)

Bug Fixes

  • index: ensure new traditional param is marked as optional ( fc600e5 )

aurelia-router 1.0.5 (2016-09-29)

Bug Fixes

  • typings: RoutableComponentCanActivate.canActivate should accept Promise<navigationcommand> as return type. ( 4460100 ), closes #401

aurelia-task-queue 1.1.0 (2016-09-29)


  • TaskQueue: expose flushing status ( fdf0bd7 )

aurelia-binding 1.0.6 (2016-09-29)

Bug Fixes

aurelia-templating 1.1.1 (2016-09-29)

Bug Fixes

aurelia-validation 0.13.0

Bug Fixes

  • ValidationParser: handle props that are only accessible via bracket syntax


  • validation-rules: permit uppercase email
  • validateTrigger: add changeOrBlur trigger
  • ValidateBindingBehavior: enable specifying validate trigger on individual bindings
  • Validator: rule prioritization and bailing
  • ValidationControllerFactory: add validator arg to createForCurrentScope

aurelia-skeleton-navigation 1.0.1

Bug Fixes

  • Fix tslint config
  • esnext-webpack: lock webpack version