You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the weeks of your assignment, you are responsible for merging our automated PRs. This means reviewing and merging dependency PRs (created on the 1 and 15).
Merge v10 compatibilities then dev dependencies
Merge v11 compatibilities then dev dependencies
Feel free to post questions in the Slack channel. If you know you’ll be out during your scheduled dates, please reach out and switch with someone else.
Sharing some notes from recent dependency updates:
Continue to downgrade @elycheea : I added a flag -m to our dependency upgrades in hopes that we no longer need to manually revert framer-motion to v6. But if we do see this upgraded anyway, we should downgrade it again.
FYI, when downgrading packages, I’ve found that I often also need to run YARN_CHECKSUM_BEHAVIOR=update yarn or the yarn.lock will remain on the later versions.
The text was updated successfully, but these errors were encountered:
On the weeks of your assignment, you are responsible for merging our automated PRs. This means reviewing and merging dependency PRs (created on the 1 and 15).
Merge v11 compatibilities then dev dependenciesFeel free to post questions in the Slack channel. If you know you’ll be out during your scheduled dates, please reach out and switch with someone else.
Sharing some notes from recent dependency updates:
Downgrades that should now be resolved
rimraf
v4 removed support for globs but it has just been reintroducedeslint-config-carbon@2.18.0
(carbon updates) resulted in some issues related to TypeScript, but should also be resolved nowaccessibility-checker
should also contain a fix ([BUG]: Latest version 3.1.41 throws an error and crashes IBMa/equal-access#1149) that allows us to upgrade it — but this one has been tricky with our monorepo so far.Continue to downgrade
@elycheea : I added a flag
-m
to our dependency upgrades in hopes that we no longer need to manually revertframer-motion
to v6. But if we do see this upgraded anyway, we should downgrade it again.FYI, when downgrading packages, I’ve found that I often also need to run
YARN_CHECKSUM_BEHAVIOR=update yarn
or theyarn.lock
will remain on the later versions.The text was updated successfully, but these errors were encountered: