Repository navigation
Toolchain update: pnpm 12.18.0 - #645
Conversation
|
@Nawid3333 CI fails on this pull request. It failed twice on this commit, so a flaky test is an unlikely cause.
The last lines of e2e (Windows, playback 2/3)The last lines of e2e (Linux, playback 1/2)The last lines of e2e (Windows, extension 1/3)The last lines of e2e (Linux, github smoke)The last lines of e2e (Windows, github smoke)The last lines of e2e (Linux, playback 2/2)The new version most likely needs changes to the code here: this pull request is labelled The pull request stays open. A new commit on it runs CI again. https://github.com/Nawid3333/FastStream/actions/runs/42580281214 |
|
@Nawid3333 CI passes on this pull request (https://github.com/Nawid3333/FastStream/actions/runs/42653567320), and every check holds: ready for you to merge. Its build of the extension is file for file the one in v1.3.82.175, the version number aside: merging it releases nothing. Closing this pull request skips this version for good; toolchain-updates.yml raises the next one. https://github.com/Nawid3333/FastStream/actions/runs/42658374701 |
pnpm 12.16.1 -> 12.18.0 (newest 12.x at least 3 days old is 12.18.0; pinned pnpm@12.16.1).
This pull request changes only
packageManagerinpackage.json, and CI has been started on it: the whole ofpnpm run verify, on Linux and on Windows.Routine:
update-prs.ymltells @Nawid3333 once CI has run whether it is ready to merge, and the merge is theirs.The lockfile is left as it is. Should this pnpm want it rewritten, CI fails at the install: run
pnpm installwith it and pushpnpm-lock.yamlhere (the pull request then waits for you).Nothing here is part of the extension: its build should come out unchanged, and a merge then releases nothing (auto-release.yml compares the builds).
Opened by https://github.com/Nawid3333/FastStream/actions/runs/42577744583