Repository navigation
build(deps): refresh pnpm and artifact actions - #79
Merged
Merged
Conversation
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
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.
What Problem This Solves
Refreshes pinned CI tooling after the main Telegram packaging repair.
User Impact
Artifact transfers gain the upstream HTTP 429 retry fix, and RTT jobs receive current pnpm fixes while preserving their existing major versions and Node runtime floors.
Why This Change Was Made
Update pnpm 12.5.1 to 12.10.1 for RTT jobs and pnpm 11.27.1 to 11.28.5 for Crabbox hydration. Update upload-artifact 7.0.1 to 7.0.2 and download-artifact 8.0.1 to 8.0.2. Keep the workflow contract and changelog in sync. No package version change or new dependencies.
Evidence
nice -n 19after Crabbox hit fleet capacity and its AWS allocation timed out.