Skip to content

fix: sync package-lock.json with @aws-sdk artifact-storage deps#629

Merged
d-klotz merged 1 commit into
nextfrom
fix/regenerate-lockfile-aws-sdk
Jul 20, 2026
Merged

fix: sync package-lock.json with @aws-sdk artifact-storage deps#629
d-klotz merged 1 commit into
nextfrom
fix/regenerate-lockfile-aws-sdk

Conversation

@d-klotz

@d-klotz d-klotz commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Summary

PR #628 (ADR-010 reporting) added @aws-sdk/client-s3 and @aws-sdk/s3-request-presigner to packages/core for report artifact storage, but the root package-lock.json was never regenerated. Since #628 merged (2026-07-17), the Release workflow's npm ci fails with:

npm error code EUSAGE
npm error `npm ci` can only install packages when your package.json and package-lock.json are in sync.
npm error Missing: @aws-sdk/s3-request-presigner ... from lock file

As a result no 2.0.0-next.105 has published — the latest published version is still next.104 (from before #628), so downstream apps can't pick up the reporting work.

Fix

Regenerated the root package-lock.json with npm 10 (npm install --package-lock-only). npm 11 lockfiles break npm ci in this repo's CI, so npm 10 was used deliberately.

  • Lockfile-only change: +59 / −37 (adds the @aws-sdk/@smithy entries, minor transitive version bumps — no dependency removals).

Test plan

  • npm ci --dry-run resolves cleanly (added 2537 packages, no EUSAGE / no "Missing:")
  • Release workflow publishes 2.0.0-next.105 on merge

🤖 Generated with Claude Code

📦 Published PR as canary version: 2.0.0--canary.629.1a7ad06.0

✨ Test out this PR locally via:

npm install @friggframework/admin-scripts@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/core@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/devtools@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/eslint-config@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/prettier-config@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/schemas@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/serverless-plugin@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/test@2.0.0--canary.629.1a7ad06.0
npm install @friggframework/ui@2.0.0--canary.629.1a7ad06.0
# or 
yarn add @friggframework/admin-scripts@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/core@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/devtools@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/eslint-config@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/prettier-config@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/schemas@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/serverless-plugin@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/test@2.0.0--canary.629.1a7ad06.0
yarn add @friggframework/ui@2.0.0--canary.629.1a7ad06.0

Version

Published prerelease version: v2.0.0-next.105

Changelog

🚀 Enhancement

  • @friggframework/admin-scripts, @friggframework/core, @friggframework/devtools
    • feat(core): implement ADR-010 reporting as an admin operation #628 (@d-klotz)

🐛 Bug Fix

Authors: 1

PR #628 added @aws-sdk/client-s3 and @aws-sdk/s3-request-presigner to
packages/core for report artifact storage, but the root package-lock.json
was never regenerated. The Release workflow's `npm ci` fails with EUSAGE
("Missing: @aws-sdk/s3-request-presigner ... from lock file"), so no
2.0.0-next.105 has published since #628 merged.

Regenerated with npm 10 (npm 11 lockfiles break `npm ci` in this repo's CI).
Verified: `npm ci --dry-run` now resolves cleanly.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@d-klotz d-klotz added release Create a release when this pr is merged prerelease This change is available in a prerelease. labels Jul 20, 2026

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Claude Code Review

Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.

Tip: disable this comment in your organization's Code Review settings.

@sonarqubecloud

Copy link
Copy Markdown

@d-klotz
d-klotz merged commit b634a23 into next Jul 20, 2026
7 of 8 checks passed
@d-klotz
d-klotz deleted the fix/regenerate-lockfile-aws-sdk branch July 20, 2026 19:16
@seanspeaks

Copy link
Copy Markdown
Contributor

🚀 PR was released in v2.0.0-next.105 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

prerelease This change is available in a prerelease. release Create a release when this pr is merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants