-
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
[6.8] Dependency updates #64936
[6.8] Dependency updates #64936
Conversation
Includes update to `geckodriver`, which uses `tar` as a transitive dependency. Now, `tar` 2.x and 4.x each resolve to the latest patch version for those majors.
Checked our usage of this and it is very simple, also did a cursory check of changes between `tar-fs` versions 1.13.0 and 1.16.3 -- did not find any changes that appeared to be breaking or that would otherwise affect our usage of this package.
The PR this backports actually updated the resolution from 1.7.0 to 2.1.1. This commit updates the resolution from 1.5.0 to 2.1.1. I checked the changelog and it doesn't appear that there are any breaking changes between 1.5.0 and 1.7.0, so this should be safe to update.
, elastic#51174) This combines backports from several PRs. elastic#46393 contained three changes to source code: * heatmap_options.html: I made the change and did a smoke-test of a heatmap using sample data, did not notice any problems. * sub_url_route_filter.js: I made this change, it is a test file so I will rely on CI to exercise it. * screenshots.js: This change appears to be superseded by another PR, elastic#46667, so I omitted the change from this backport.
This is a transitive dependency. It has been updated in newer versions of Kibana, but I could not find the PR that changed the master branch.
This is a transitive dependency. It has been updated in newer versions of Kibana, but I could not find the PR that changed the master branch.
This is a transitive dependency.
Note: the PRs this backports also included updates to the `@types/papaparse` package, but Kibana 6.8 does not use that package. So this commit ignores that package.
In the PR this backports, the `pivotal-ui` package is no longer in use and could be removed. I double-checked and Kibana 6.8 does not use this package either, so we can backport that PR.
In the PR this backports, the `react-markdown-renderer` package is no longer in use and could be removed. I double-checked and Kibana 6.8 does not use this package either, so we can backport that PR.
This is a transitive dependency.
This is a transitive dependency.
Note: elastic#61209 also changes transitive dependency resolutions for the `mkdirp` package; this commit omits those changes.
Also condensed other transitive dependency resolutions so they all use the same patch version.
This is a transitive dependency.
This is a transitive dependency.
I only updated the direct dependency. There are a couple of transitive dependencies which still resolve to older versions, but these are sourced from devDependencies and not a priority to be updated.
Note, there is still a transitive dependency that resolves to an older version. I did not want to upgrade this as it may break things, and it's part of the `@elastic/eui` package which has been updated in newer versions of Kibana.
74f47b3
to
eef653f
Compare
eef653f was intended to update `jquery` to 3.4.1, but it actually updated to 3.5.0. That version includes a breaking change that causes as-of-yet unknown issues, including CI failures. This commit downgrades `jquery` to 3.4.1, which is known to work with Kibana 7.2+.
retest |
I am getting errors when I run
This matches what we are seeing in the CI failure here. I tried reverting all commits and I am still getting that error. Don't know what exactly is going on, but I don't think it's being caused by any of the commits in this PR. Will need to revisit it next week. Edit: this appears to be the same issue: #24684 |
…astic#46393, elastic#51174)" This reverts commit c191eae.
It appears that c191eae is responsible for two CI failures:
Since that's just what CI is catching, and the Angular update could (probably does) have broader impact, I think it's best to revert that change for now, and revisit later if we deem it necessary. |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
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
This PR manually backports several dependency updates. See each commit message for details.
Additional notes:
mixin-deep
package update was updated from 1.3.1 to 1.3.2 in Kibana 7.5+ (via Updating mixin-deep #46412).packages/kbn-pm/dist/index.js
file (rebuilt using theyarn kbn run build -i @kbn/pm
command). These changes match those from the original PR.tar
package was updated from 2.2.0 to 4.4.8 in Kibana 7.2+ (via Update archiving dependencies #35896), but this entailed several additional changes to code that uses this package. Instead, I opted to update this package's patch version to 2.2.2.tar-fs
package was removed in Kibana 7.2+ (via Update archiving dependencies #35896), but it is still used in Kibana 6.8, so I updated it here.set-value
package was updated in the master branch at some point (verified by examining ouryarn.lock
file), but I was not able to easily identify which PR updated this because it is a transitive dependency several layers deep. I updated the resolution to the latest patch version.packages/kbn-pm/dist/index.js
file (rebuilt using theyarn kbn run build -i @kbn/pm
command).extend
package was updated in the master branch at some point (verified by examining ouryarn.lock
file), but I was not able to easily identify which PR updated this because it is a transitive dependency several layers deep. I updated the resolution to the latest patch version.