Closed agilgur5 closed 3 months ago
Fixed merge conflicts with #509.
There's a new warning during the install that seems to be because dependabot just merged #539 and #541 (they were created before #537 was merged), which are almost certainly not compatible 😕 . They seem to have finally passed CI because #509 removed some old deps. That does bolster the case of #537
lint
is weirdly erroring here but not in other PRs that similarly don't change source code... strange...
Raised #543 for that since it's independent of this PR. Will have to rebase once that's merged
Stale pull request message
lint
is weirdly erroring here but not in other PRs that similarly don't change source code... strange...Raised #543 for that since it's independent of this PR. Will have to rebase once that's merged
I may have figured out why that's happening, some of the ESLint deps ended up getting upgraded a few minors in the yarn.lock
in this PR. Let me fix that
Perhaps may have been due to a bad merge conflict resolution with #509
Originally started as a follow-up to https://github.com/argoproj/argo-workflows/pull/12097#discussion_r1375279098 on
moment-timezone
, but there were actually much more unused deps to pruneMotivation
Deps
resolutions
lodash
resolution is no longer needed as all deps are compatible withlodash
^4
141 added it and it may have been necessary for some of the
lodash
v3 deps there, but this codebase no longer has anylodash
v3 deps@types/history
is already using^4.7.8
without the resolution71 added it while also upgrading the devDep; only upgrading the devDep was necessary
Modifications
moment-timezone
fromdependencies
devDependencies
resolutions
Verification
Notes to Reviewers
I actually wrote this on Jan 6th (see the commits), the same time as my other PRs, but I thought this would merge conflict with some of them, so I didn't create the PR, intending to rebase with those once they were merged. This actually seems to not conflict with #511 at all as far as I can tell, so creating the PR now, and because it's already been over a month with no review/merge 😕 EDIT: Welp, they actually conflicted with #509. I have a feeling past me predicted that and then I just forgot over the past month