Repository navigation
Promote staging CLI smoke tooling to master - #31
Merged
Merged
Conversation
* FAL-311: Add isolated read-only CLI live smoke coverage * Run package validation through portable Node entrypoints * docs: clarify Factory and platform smoke verification * docs: distinguish routine CI from platform smoke proof
…c-20261010-master # Conflicts: # docs/development.md
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
1 participant
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.
Promote the reviewed staging CLI smoke tooling into master, preserving the existing 0.4.1-rc.1 package version and master-only Command behavior. The development guide retains both the release policy and the new isolated smoke-check documentation.
Carries CLI PR 28. No public Command or API contract changes; no consumer artifact refresh is needed.
Validation:
npm ci,npm run check, andnpm run test:packagepassed. Both packed npm names installed and ran in a clean local consumer. No authenticated live smoke or npm publication was run; production publishing remains disabled.