Repository navigation
ci: remove the one-off first publish workflow - #487
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.
#483's workflow did its job. Run 41092417453 published
@chatcops/ingest0.1.0,cli0.1.0,store-cloudflare,store-postgres,store-redisandstore-sqlite0.2.0, andstore-upstash-vector0.1.0. All have provenance andpeerDependencieson@chatcops/core^0.6.0.From here on they'll release through
release.ymlwith trusted publishing, like core, server and widget, so the workflow and theNPM_TOKENsecret it used can go. The token was short-lived and gets deleted on npm.