ci: bootstrap broker and Devframe npm packages - #73
Merged
Merged
Conversation
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.
Background (Why)
The broker and Devframe packages must exist on npm before their trusted publishers can be configured.
Changes (What)
Add a temporary manual workflow restricted to main and the npm environment. It builds and publishes only those two packages at 0.0.0 under the bootstrap tag using the temporary environment token and provenance. No version changes are committed. Remove this workflow after the two trusted publishers are configured.
Verification (Testing)
Workflow lint, git diff checks and broker type checking pass. Execution waits for the npm setup checkpoint; the merged implementation passed full CI.