Skip to content

chore(sdk): make insight package release-ready for first npm publish#726

Merged
ParidelPooya merged 1 commit into
mainfrom
fix/insight-release-readiness
Jul 16, 2026
Merged

chore(sdk): make insight package release-ready for first npm publish#726
ParidelPooya merged 1 commit into
mainfrom
fix/insight-release-readiness

Conversation

@ParidelPooya

Copy link
Copy Markdown
Contributor
  • Add explicit "private": false to aws-durable-execution-sdk-js-insight package.json, matching the other publishable packages in the repo.
  • Widen the @aws/durable-execution-sdk-js peer dependency range from

    =2.0.0-alpha.1 to >=2.1.0 (current core SDK version) so the floor
    tracks what's actually been released.

  • Add packages/aws-durable-execution-sdk-js-insight to the PACKAGES array in iterate-publish-npm.sh so the npm-publish workflow actually publishes it on release (it was previously excluded, so a release would have silently skipped it).

The cdk/ subpackage already has "private": true and is intentionally not published to npm; customers consume it from the GitHub repo.

- Add explicit "private": false to aws-durable-execution-sdk-js-insight
  package.json, matching the other publishable packages in the repo.
- Widen the @aws/durable-execution-sdk-js peer dependency range from
  >=2.0.0-alpha.1 to >=2.1.0 (current core SDK version) so the floor
  tracks what's actually been released.
- Add packages/aws-durable-execution-sdk-js-insight to the PACKAGES
  array in iterate-publish-npm.sh so the npm-publish workflow actually
  publishes it on release (it was previously excluded, so a release
  would have silently skipped it).

The cdk/ subpackage already has "private": true and is intentionally
not published to npm; customers consume it from the GitHub repo.
@ParidelPooya
ParidelPooya marked this pull request as ready for review July 16, 2026 18:15
@ParidelPooya
ParidelPooya merged commit 1eee0d8 into main Jul 16, 2026
16 checks passed
@ParidelPooya
ParidelPooya deleted the fix/insight-release-readiness branch July 16, 2026 18:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants