fix: complete partial v5-stable LTS release (publish remaining packages)

[osama-rizk]

What

Triggers a full v5-stable LTS release to complete the previous partial publish. Adds a one-line no-op comment to the entry file of every publishable package so lerna publish --conventional-commits detects all of them as changed and republishes the entire v5 suite to the stable-5 dist-tag at a fresh, consistent version. No functional code change.

Why this is needed

The prior release run published only part of the suite. lerna publish --dist-tag=stable-5 aborted partway when the postpublish dist-tag hook on amazon-cognito-identity-js failed (transient npm error), leaving npm split:

• Published: amazon-cognito-identity-js@6.3.17, @aws-amplify/analytics@6.5.18, @aws-amplify/api-rest@3.5.19, @aws-amplify/notifications@1.6.19, @aws-amplify/storage@5.9.21.
• NOT published: aws-amplify@5.3.34, @aws-amplify/datastore@4.7.23 (the RN uuid-v11 fix, fix(datastore): load react-native-get-random-values for uuid v11 on React Native #14842), @aws-amplify/datastore-storage-adapter@2.0.66, @aws-amplify/api@5.4.22, @aws-amplify/auth@5.6.20, @aws-amplify/predictions@5.5.23, @aws-amplify/pubsub@5.6.7.

Because the git tags 5.3.34/4.7.23 were already pushed, a plain re-run of the publish job finds "no changed packages" and publishes nothing. A fix:-typed commit touching every package is the way to make --conventional-commits re-release the full suite through the existing merge-to-release pipeline.

Effect on merge

• fix: type → lerna bumps all packages a patch level and publishes them to stable-5.
• The 7 missing packages reach npm; the ~6 already-published ones are re-published at the new patch version. End state: the whole v5 suite is consistent on stable-5 with the uuid-v11 RN fix included.

⚠️ Reviewer / release-owner notes

• Each change is a pure +2/-0 comment append (blank line + comment) on src/index.ts (or src/index.js for cognito). 20 packages touched; no code logic altered.
• This intentionally re-publishes already-live packages at a new patch version (e.g. storage@5.9.22, cognito@6.3.18) to keep the suite version-aligned; versions 5.3.34/4.7.23 remain tagged-but-unpublished.
• Merging pushes to v5-stable and publishes to production npm stable-5 — irreversible (72h unpublish window). Please confirm before merging.

Failed release job (context)

The partial publish that this PR completes occurred in the release / Publish to Amplify Package job of the LTS release run:

• Failed job: https://github.com/aws-amplify/amplify-js/actions/runs/27424967279/job/81077875199

In that job, lerna publish --dist-tag=stable-5 began publishing and then aborted when the postpublish lifecycle hook on amazon-cognito-identity-js (npm dist-tag add …) errored:

lerna success published @aws-amplify/notifications 1.6.19
lerna success published @aws-amplify/analytics 6.5.18
lerna success published @aws-amplify/api-rest 3.5.19
...
lerna info lifecycle amazon-cognito-identity-js@6.3.17~postpublish: amazon-cognito-identity-js@6.3.17
> npm dist-tag add $npm_package_name@$npm_package_version latest
lerna ERR! lifecycle "postpublish" errored in "amazon-cognito-identity-js", exiting 1

Because lerna treats a failed lifecycle hook as fatal, the remaining packages were left unpublished — and since the version-bump commit and git tags (5.3.34 / 4.7.23) were already pushed, simply re-running that job publishes nothing (--conventional-commits sees no changed packages since the existing tags). Hence this fresh fix: commit to re-trigger a full release.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2fe3050

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR