Skip to content

chore(js): Unstale yarn lock#2607

Merged
Lms24 merged 2 commits intomasterfrom
lms/chore-unstale-yarn-lock
Jul 15, 2025
Merged

chore(js): Unstale yarn lock#2607
Lms24 merged 2 commits intomasterfrom
lms/chore-unstale-yarn-lock

Conversation

@Lms24
Copy link
Copy Markdown
Member

@Lms24 Lms24 commented Jul 15, 2025

Looks like yarn.lock was stale and missed am entry for a new(?) binary

@Lms24 Lms24 requested a review from szokeasaurusrex as a code owner July 15, 2025 11:52
Copy link
Copy Markdown
Member

@szokeasaurusrex szokeasaurusrex left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

new binary is the Windows on ARM binary.

Any clue why this was not getting updated? It probably should happen automatically, right?

@Lms24
Copy link
Copy Markdown
Member Author

Lms24 commented Jul 15, 2025

You have to run yarn install once locally and push up the changes whenever you add pacakge (which I guess is what happened here). Usually, when you update or add a dependency, yarn.lock updates automatically, yes.

@Lms24 Lms24 enabled auto-merge (squash) July 15, 2025 12:35
@Lms24 Lms24 merged commit 0159d3c into master Jul 15, 2025
25 checks passed
@Lms24 Lms24 deleted the lms/chore-unstale-yarn-lock branch July 15, 2025 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants