We released Angular UI-Router 1.0.0-rc.1 today. This release indicates that the APIs are not expected to change before the final release of ui-router 1.0.
This release includes more breaking changes than usual. We are making an effort to call out more breaking changes that could potentially break end user applications, even if the prior behavior was unspecified.
Changes in RC.1
RC.1 is a major update, which includes many bug fixes and lots of new features.
Please see the release notes for detailed information, including the breaking changes.
During the betas, both
ui-router-ng2 and the
angular-ui-router for ng1 code were built from the same repository.
This seemed like a good idea at the time because it allowed PRs to a monolithic repository.
However, over time it became apparent that hosting both codebases together was not sustainable.
So, we split the repositories into:
angular-ui-router: UI-Router for AngularJS 1
ui-router-ng2: UI-Router for Angular (2.0 and above)
ui-router-core: UI-Router core
This release is the first one built from the modular UI-Router repositories.
This release (1.0.0-rc.1) of Angular UI-Router is not accompanied by a release of UI-Router for Angular (2+)+. Going forward, the release schedules for AngularJS and Angular (2+) will no longer coincide.
If you haven’t considered upgrading to UI-Router 1.0, now is the time to start planning. There are some breaking changes listed, but the should be fairly minimal for the typical UI-Router application. Please follow the migration guide when upgrading.