chore(deps): update yarn to v4.12.0 #24
Conversation
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
8 times, most recently
from
11ee4d6 to
c93e29c
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
5 times, most recently
from
9007cb0 to
0ea9b94
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
5 times, most recently
from
d1ec254 to
c78fa7c
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
12 times, most recently
from
385b5e0 to
1a6f7af
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
4 times, most recently
from
71a3b71 to
afac531
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
3 times, most recently
from
3ad5206 to
aa92c73
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
4 times, most recently
from
fa27047 to
9ad8db7
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
5 times, most recently
from
a3666ad to
467bf94
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
3 times, most recently
from
6e82d98 to
47c6449
Compare
renovate
bot
force-pushed
the
renovate/yarn-monorepo
branch
from
47c6449 to
2391fa9
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
…still a rule for yarn caches though)
| .yarn | ||
| !.yarn/releases |
There was a problem hiding this comment.
Re https://github.com/mitodl/hq/discussions/9883#discussioncomment-15500633
- Questions: chore(deps): update yarn to v4.12.0 learn-ai#24 - needs a rubber stamp; the
.gitignorewas breaking yarn upgrades so did it and fixed the ignor
In what sense was yarn breaking?
These gitignores are desirable... yarn install leaves a file .yarn/install-state.gz that we won't want to commit. (It may leave other files, too, sometimes. I forget.)
There was a problem hiding this comment.
The negation rule in the gitignore wasn't working, so the updated version of yarn wasn't getting committed back. So, when CI/etc. ran, the configs all were set to look for yarn 4.12 and not seeing it, because it wasn't getting committed. I'm not sure why this is happening. I did a bunch of working through gitignore rules and testing and it seems like this should work, but yet it kept ignoring everything in frontend-demo/.yarn/releases. (Maybe there's something stuck in the git metadata that's causing this behavior? I'll do some further digging..)
ChristopherChudzicki
left a comment
ChristopherChudzicki
left a comment
There was a problem hiding this comment.
Meant to mark comment as blocking
…aged stuff in it); use the rules from the Yarn docs
2 participants
This PR contains the following updates:
4.5.1→4.12.0Release Notes
yarnpkg/berry (yarn)
v4.12.0Compare Source
v4.11.0Compare Source
v4.10.3Compare Source
v4.10.2Compare Source
v4.10.1Compare Source
v4.10.0Compare Source
v4.9.4Compare Source
v4.9.3Compare Source
v4.9.2Compare Source
v4.9.1Compare Source
v4.9.0Compare Source
v4.8.1Compare Source
v4.8.0Compare Source
v4.7.0Compare Source
v4.6.0Compare Source
v4.5.3Compare Source
v4.5.2Compare Source
Configuration
📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.