fix: regenerate Kotlin Wasm yarn lock in dependabot automation - #61
Merged
Conversation
zigzago
force-pushed
the
fix/wasm-yarn-lock-regeneration
branch
2 times, most recently
from
September 4, 2026 08:58
42e9ec7 to
2bfaf50
Compare
The dependabot-yarn-lock workflow only ran kotlinUpgradeYarnLock (JS), leaving e2e-split/kotlin-js-store/wasm/yarn.lock stale whenever a dependency bump changed the Wasm target's npm dependency graph. This caused kotlinWasmStoreYarnLock to fail in the E2E Split-by-client job (seen on PR #59 after the ktor bump).
zigzago
force-pushed
the
fix/wasm-yarn-lock-regeneration
branch
from
September 4, 2026 08:59
2bfaf50 to
8cb46a1
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dependabot-yarn-lock.ymlworkflow's "Regenerate Kotlin yarn lock" step only rankotlinUpgradeYarnLock(JS target), neverkotlinWasmUpgradeYarnLock(Wasm target).e2e-split/kotlin-js-store/wasm/yarn.lockwent stale, andkotlinWasmStoreYarnLockfailed theE2E Split-by-clientjob withLock file was changed. Run the kotlinWasmUpgradeYarnLock task to actualize lock file.chore: update Kotlin yarn lock, but only touched the JS lock file, leaving the Wasm lock stale and the job red.kotlinUpgradeYarnLockandkotlinWasmUpgradeYarnLockin that step. The commit step already handled both lock files, it just never got a Wasm-side change to commit.