feat(ci): publish plugin marketplace on release#1540
Conversation
- Add plugin marketplace build step to release workflow - Upload marketplace artifacts to GitHub Release - Make build script skip missing sources gracefully
🦋 Changeset detectedLatest commit: 47e7436 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 47e743611d
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| publish-plugin-marketplace: | ||
| name: Publish plugin marketplace | ||
| needs: release | ||
| if: needs.release.outputs.packages_published == 'true' |
There was a problem hiding this comment.
When Changesets publishes any package other than @moonshot-ai/kimi-code, packages_published is still true, but apps/kimi-code/scripts/native/resolve-release.mjs emits should_publish=false and a fallback tag based on the current Kimi package version. This new job would then upload the freshly built marketplace to a stale or nonexistent Kimi Code release tag (with --clobber, potentially overwriting the previous release asset) instead of skipping like publish-native-assets does; gate this on needs.release.outputs.kimi_native_release == 'true' or an equivalent Kimi-package-published output.
Useful? React with 👍 / 👎.
1 participant
This PR adds plugin marketplace publishing to the release workflow.
Changes
build:plugin-marketplacestep to the release workflowbuild-plugin-marketplace-cdnscript skip missing sources gracefully instead of failingWhy
Currently the plugin marketplace needs to be built and published manually. This automates the process so every release includes the latest marketplace data.
Testing