ci: publish @aerokit/test to npm on release - #6324
Merged
Merged
Conversation
The generic Playwright runner for generated <name>.test manifests (npm/test) landed without a publish step - the release publishes @dirigiblelabs/dirigible, dirigible-cli and @aerokit/sdk only, so the package was unreachable from npmjs and consumers had to vendor it via a file: dependency. Mirror the @aerokit/sdk steps: stamp the release version, npm publish --access public from ./npm/test. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The generic Playwright runner for generated
<name>.testmanifests (npm/test, added with the AppTest generator wave) has no publish step in the release workflow - only@dirigiblelabs/dirigible,@dirigiblelabs/dirigible-cliand@aerokit/sdkare published, so@aerokit/testis unreachable from npmjs and consumers must vendor it via afile:dependency.This mirrors the
@aerokit/sdkstep pair for./npm/test: stamp the release version, thennpm publish --access public(same npmjs token, the@aerokitscope already exists). First actual publish happens with the next release run.🤖 Generated with Claude Code