Repository navigation
chore(api): regenerate the spec for ReportScheduleRestApi.report_format - #43910
Merged
villebro merged 1 commit intoSep 4, 2026
Merged
Conversation
apache#43365 added report_format to the report schedule list columns without regenerating, so the API staleness check fails on master.
Contributor
|
Bito Automatic Review Skipped - Files Excluded |
villebro
approved these changes
Sep 4, 2026
✅ Deploy Preview for superset-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
6 tasks
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.
SUMMARY
Unblocks the API staleness check on
master. #43365 addedreport_formattoReportScheduleRestApi's list columns without regeneratingopenapi.json, soReportScheduleRestApi.get_listis missing the field.The check was already on
masterwhen #43365 merged, but that PR's last CI run predated it and GitHub does not re-run workflows at merge time, so the check never reported there. Any PR whose latest run predates #43841 can still land stale this way; enabling "require branches to be up to date before merging" for the check would close it, otherwise it self-heals as open PRs rebase.TESTING INSTRUCTIONS
ADDITIONAL INFORMATION