-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade axios
dependency (0.21.1
→ 0.27.2
).
#111655
Conversation
Pinging @elastic/kibana-operations (Team:Operations) |
@elasticmachine merge upstream |
This comment has been minimized.
This comment has been minimized.
This break is somewhere in the 0.21.2 release. Taking a look at our test interceptors.. |
Looks similar to https://github.com/axios/axios/pull/3688/files#r706543576 |
@jbudz this comment claims that the problem was fixed in axios@v0.21.3. Can we resurrect this PR and upgrade/retest? It would be great to get this shipped with the 7.17 release. |
Pinging @elastic/apm-ui (Team:apm) |
Pinging @elastic/fleet (Team:Fleet) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🌔 🚀 ✨ LGTM ✨ 🚀 🌔
(Sec Telemetry - after comments from @azasypkin are addressed).
I think I would like to move off axios and use node-fetch or something for sec-telemetry. I might refactor this once this has been sorted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fleet changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ResponseOps changes LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Presentation team test syntax change LGTM! Code only review
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flakyFailed CI StepsMetrics [docs]Module Count
Async chunks
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Since the PR has an absolute majority of the approvals I'm going to merge it now to reduce the risk of conflicts with the upstream. @parkiino feel free to leave your feedback after the merge if any and I'll handle it separately. |
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
…132110) * Upgrade `axios` dependency (`0.21.1` → `0.27.2`). (#111655) Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> (cherry picked from commit b191f14) # Conflicts: # packages/kbn-pm/dist/index.js # x-pack/plugins/actions/server/builtin_action_types/servicenow/utils.test.ts # x-pack/plugins/actions/server/builtin_action_types/servicenow/utils.ts # x-pack/plugins/fleet/server/telemetry/sender.ts # x-pack/plugins/osquery/server/lib/telemetry/sender.ts # x-pack/plugins/security_solution/scripts/endpoint/blocklists/index.ts # x-pack/plugins/security_solution/server/lib/telemetry/sender.ts # x-pack/plugins/synthetics/server/lib/telemetry/sender.ts # x-pack/test/performance/services/auth.ts # x-pack/test/ui_capabilities/common/services/ui_capabilities.ts # yarn.lock * Update yarn.lock Co-authored-by: Jonathan Budzenski <jon@elastic.co>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine to me. sorry i didn't get to it earlier
Summary
Upgrade
axios
dependency (0.21.1
→0.27.2
).Change log: https://github.com/axios/axios/blob/master/CHANGELOG.md
Note to reviewers: Most of the breaking changes are related to Axios types, but there are some notable breaking changes in 0.25.0 and 0.27.0 releases that you might want to verify in the scope of your specific use cases.