chore(deps): bump @bower_components/jquery-ui from 1.10.0 to 1.12.1 in /build#41647
Conversation
Bumps [@bower_components/jquery-ui](https://github.com/components/jqueryui) from 1.10.0 to 1.12.1. - [Release notes](https://github.com/components/jqueryui/releases) - [Commits](components/jqueryui@4c0bac6...44ecf37) --- updated-dependencies: - dependency-name: "@bower_components/jquery-ui" dependency-version: 44ecf3794cc56b65954cc19737234a3119d036cc dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
DeepDiver1975
left a comment
DeepDiver1975
left a comment
There was a problem hiding this comment.
🤖 Automated code review by Claude Code review agent
Dependabot bump of @bower_components/jquery-ui 1.10.0 → 1.12.1. Diff is minimal and clean: only build/package.json (bower manifest pin) and build/yarn.lock (resolved git ref/uid). No large vendored JS/CSS asset blob is committed here — assets are fetched from the new git ref at build time, so there is nothing to inspect in the diff.
Heads-up: 1.10→1.12 is a real frontend jump (1.12 dropped some deprecated widgets/options), so there is a non-trivial web-UI regression surface. For a maintenance-mode repo this is acceptable provided CI is green — treat the frontend smoke/CI run as the gate, and ideally a quick manual click-through of jquery-ui-driven UI (datepicker, dialogs, sortable, autocomplete) before merge.
Verdict: approve-with-CI-gate.
1 participant
Bumps @bower_components/jquery-ui from 1.10.0 to 1.12.1.
Commits
44ecf37Merge pull request #60 from danielnixon/patch-178c6194Add license to bower.jsondec4c50jQuery UI 1.12.12c9359areadd splitted base-theme css files99c8c1areadd corrected package.json51d123ajQuery UI 1.12.081fac70Merge pull request #50 from umeboshi2/gitignore-is-only-half-the-battle-remov...70bac28remove unnecessary filec34f8dbjQuery UI 1.11.47e2d6bemissed updating *.jsonDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)