Repository navigation
ci(platform): sync asyncapi.json from production every week - #318
Draft
amitbardos wants to merge 1 commit into
Draft
amitbardos wants to merge 1 commit into
amitbardos wants to merge 1 commit into
Conversation
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.53-pr.318.571c999Prefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.53-pr.318.571c999"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.53-pr.318.571c999"
}
}
Preview published to npm registry — try new features instantly! |
amitbardos
force-pushed
the
amitb/platform-asyncapi-workflow
branch
from
October 11, 2026 12:47
399cb39 to
b7fee6d
Compare
A weekly workflow (and workflow_dispatch) fetches https://app.base44.com/api/asyncapi.json, regenerates the event types, builds the docs and runs the Platform SDK tests, and opens or updates one rolling PR on bot/platform-asyncapi-sync only when asyncapi.json or the generated types changed. It closes that PR when main already matches production. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
amitbardos
force-pushed
the
amitb/platform-asyncapi-workflow
branch
from
October 11, 2026 12:51
b7fee6d to
1ecd050
Compare
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.
Stacked on #313. Merge it after base44-dev/apper#29607 deploys. Split out of #313 so the docs and
getSessionthere don't wait for the deploy.What
.github/workflows/sync-asyncapi.ymlruns weekly on Mondays at 06:00 UTC and onworkflow_dispatch:npm run sync:asyncapiagainsthttps://app.base44.com/api/asyncapi.json, thengen:events.packages/platform/asyncapi.jsonorbuilder.events.generated.tschanged, it runscreate-docsandnpm testfor the Platform SDK.bot/platform-asyncapi-sync. The branch is rebuilt frommainon every run, so it never conflicts.It uses only what the repo already uses: the pinned
actions/checkoutandactions/setup-node, the mandatory Wix gateway proxy, and the runner'sgh. No new dependencies. CI checks the proxy step withcheck_wix_proxy_steps.py(check-wix-proxy.yml).Before merging
Production serves the events only once base44-dev/apper#29607 deploys. Until then the sync script finds no messages and exits with an error, so a scheduled run fails. After the deploy, run
npm run sync:asyncapilocally against production and check thatasyncapi.jsonhas no diff. Then merge, and trigger the workflow once by hand.🤖 Generated with Claude Code