Skip to content

Update dependency angular-ui-router to ^0.3.0 - #58

Open
dev-mend-for-github-com[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/angular-ui-router-0.x
Open

Update dependency angular-ui-router to ^0.3.0#58
dev-mend-for-github-com[bot] wants to merge 1 commit into
mainfrom
whitesource-remediate/angular-ui-router-0.x

Conversation

@dev-mend-for-github-com

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
angular-ui-router (source) dependencies minor ^0.2.18^0.3.0

By merging this PR, the below vulnerabilities will be automatically resolved:

Severity CVSS Score Vulnerability
High High 7.2 CVE-2026-11998

Release Notes

angular-ui/ui-router (angular-ui-router)

v0.3.0: legacy maintenance release

Compare Source

(2016-05-14) diff

This is a release of the legacy branch, primarily to fix the $scope destroy ordering issues introduced in 0.2.16, as well as adding $scope.$resolve to enable "route-to-component-template".

We recommend all users to try the 1.0.0 alpha and report any issues it causes with your application. Read the known breaking changes between the legacy and 1.0 branches.

BC-BREAK

In 0.2.16 we delayed the ui-view $scope destroy() until after all animations were completed. This was a mistake, and we're reverting it in 0.3.0.

The original issue that we tried to address: #​1643

We are switching back to 0.2.15 behavior. The scope is now destroyed as soon as the view is swapped out. This allows cleanup to happen in response
to the $destroy event. If you need to do things after the animation, we've put the promise on the element.data('$uiView') in #​2562

Bug Fixes
  • state: Inject $state at runtime to force initialization (de3a04a7, closes #​2574)
  • ui-sref: update ui-sref-active/eq info when params change When ui-state dynamicly changes (9698ec4d, closes #​2554)
  • ui-state: update ui-sref-active/eq info when ui-state dynamicly changes watchers, make sur (abb3deba, closes #​2488)
Features
  • resolve: Put resolve values on the scope as $scope.$resolve

    This enables easier "routing-to-component-template", i.e.,

    .state({ name: 'foo', 
      resolve: { thing: (MyService) => MyService.getThing() }
      template: '<my-component component-input="$resolve.thing"></my-component>'
    });
    
  • uiView:


  • If you want to rebase/retry this PR, check this box

@dev-mend-for-github-com dev-mend-for-github-com Bot added the security fix Security fix generated by Mend label Jul 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

security fix Security fix generated by Mend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants