Repository navigation
Publish v0.2.0 to GitHub Packages and create installable release - #4
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
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.
Adds one-shot, version-locked publishing workflow for @firexcore/agent-orbs@0.2.0. Runs npm check plus ESM/CJS export smoke for MonoLatticeOrb, InteractiveOrb, AgentOrb, ThinkingOrb; packs and verifies license/distributable contents; publishes to the existing GitHub Packages npm registry with GITHUB_TOKEN; then creates the versioned GitHub Release and tarball. Updates README and changelog to v0.2.0. Does not falsely claim distribution on npmjs.org. Triggered only by merging this workflow into main or manual dispatch.