Remove automatic npm publication - #351
Merged
Merged
Conversation
roackb2
marked this pull request as ready for review
August 15, 2026 07:10
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
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.
What changed
@heddleagent/*packagesWhy
npm publication still requires operator authentication, so merging to
mainmust not pretend that publishing, tagging, or GitHub release creation completed automatically. This returns releases to a simple and truthful manual boundary.Impact
Package contents, versions, exports, and normal build/test behavior are unchanged. Future releases require an explicit annotated tag, GitHub release, and manual
npm publishcommand.Validation
yarn lintyarn test:unit(137 files, 904 tests)yarn package-family:verifynode --check scripts/verify-execution-host-client-pack.mjsnode --check scripts/verify-postgres-pack.mjsgit diff --check