Repository navigation
chore: regenerate generated files - #927
Merged
Merged
Conversation
Regenerated from main at 485c14c by .github/workflows/generated-readmes.yml (node scripts/gen-web-src-readme.ts, node scripts/gen-engine-modules.ts and pnpm run build:mcp-fn, build:ca-fn and build:penpot-fn).
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.
Regenerated from main at 485c14c by
.github/workflows/generated-readmes.yml. Onlyshells/web/src/README.md(code-map stats),engine/README.md(module map) and the generatedapi/function bundles change.Pull requests no longer have to commit these generated files, because every merge moved their counts and forced a rebase and a full CI run on every other open web pull request. Each push to main that changes their inputs rebuilds this branch from that main, so this pull request never conflicts and always matches the newest main.
The branch and this pull request are made with the lolly-automation App, so CI runs as for any other pull request, and auto-merge lands it once the required
qualificationcheck passes. Until it merges, the strictapi bundle driftcheck keeps the main push run red when the bundles are stale, so no deployment or release can take that commit.