backport fix to release branch: pin @aws-sdk/client-s3 and enforce frozen lockfile#197
Merged
Conversation
The scripts image build (`tsc -p .`) was failing with: @aws-sdk/client-s3/dist-types/S3Client.d.ts: error TS2307: Cannot find module '@aws-sdk/middleware-sdk-s3/s3' @aws-sdk/client-s3@3.1062.0 references the `@aws-sdk/middleware-sdk-s3/s3` subpath in its emitted .d.ts. That subpath is only reachable via the package's `exports` map, which TypeScript's classic `moduleResolution: node` (used here) does not read, so type resolution fails. The committed yarn.lock had no @aws-sdk entries and the Dockerfile ran a non-frozen `yarn`, so `^3.982.0` re-resolved fresh on every build and floated up into the broken 3.1062.0. Pin client-s3 to an exact known-good version (3.1050.0, the last release whose .d.ts does not use the unreadable subpath), lock the full @aws-sdk tree, and switch the install to `yarn install --frozen-lockfile` so the build is reproducible and cannot drift again. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The prysm_validator service floated on the `stable` tag while prysmctl and beacon-chain are pinned to v6.1.1. `stable` rolled forward to v7.1.4, which introduces the `gloas` fork (version 0x07000000). The v6.1.1 genesis and beacon-chain configs have no gloas entry, so the validator aborts at startup with "conflicting fork version schedule" and every PoS run fails. Pin the validator to v6.1.1 to match the rest of the Prysm stack. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Pulled in by #197
The scripts image build (
tsc -p .) was failing with:@aws-sdk/client-s3/dist-types/S3Client.d.ts: error TS2307:
Cannot find module '@aws-sdk/middleware-sdk-s3/s3'
@aws-sdk/client-s3@3.1062.0 references the
@aws-sdk/middleware-sdk-s3/s3subpath in its emitted .d.ts. That subpath is only reachable via the package'sexportsmap, which TypeScript's classicmoduleResolution: node(used here) does not read, so type resolution fails.The committed yarn.lock had no @aws-sdk entries and the Dockerfile ran a non-frozen
yarn, so^3.982.0re-resolved fresh on every build and floated up into the broken 3.1062.0.Pin client-s3 to an exact known-good version (3.1050.0, the last release whose .d.ts does not use the unreadable subpath), lock the full @aws-sdk tree, and switch the install to
yarn install --frozen-lockfileso the build is reproducible and cannot drift again.