Skip to content

chore: release shared packages at 0.0.2 - #6

Merged
anilkreddy merged 1 commit into
mainfrom
release/packages-0.0.2
Nov 10, 2026
Merged

anilkreddy merged 1 commit into
mainfrom
release/packages-0.0.2

Conversation

@anilkreddy

Copy link
Copy Markdown
Contributor

Summary

Prepare both shared packages at 0.0.2 after merging Dependabot #2 (globals 17.14.0) and #3 (@types/node 26.6.6, undici-types 8.9.0). Refresh changelogs, current-version examples and actual third-party dependency notices. Distribution stays on the preview channel with package-specific prerelease tags/Releases.

Runtime Node stays pinned to 24.21.0. All 37 compiled JavaScript, declaration and schema files are byte-identical before/after the development dependency updates; no package runtime API or schema changes.

Validation

  • Frozen installation and full local pnpm quality passed.
  • 207 tests passed; independent package coverage thresholds passed.
  • Both tarballs inspected, installed and imported; declarations and schema exports verified.
  • Public scan passed; dependency audit reports no known vulnerabilities.

Merge after current-head CI/CodeQL pass, then run guarded publication for each 0.0.2 package followed by package-specific GitHub Releases. This is the owner-requested maintenance release; no reservation workflow is needed and 0.0.1 remains immutable.

@anilkreddy
anilkreddy merged commit a5018a0 into main Nov 10, 2026
6 checks passed
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.

1 participant