mikebridge opened a new pull request, #43776: URL: https://github.com/apache/superset/pull/43776
### SUMMARY Docs-only follow-up to #43350. With version history enabled, the first save through the chart editor of a chart whose settings were written by something other than the current editor — an older Superset version, an import, or the API — can still record a one-time settings-migration entry next to the user's own change (legacy keys such as `granularity_sqla` / `time_range` being rewritten to their modern form). #43350 suppressed the much larger default-stamping noise; this remaining migration entry is the deliberate boundary of that fix, happens at most once per chart per upgrade, and later saves record only what the user changed. This PR says so in the two places users and support will look: the version-history docs page and `UPDATING.md`. No code changes. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF N/A (documentation only). ### TESTING INSTRUCTIONS 1. Read the new paragraph in `docs/docs/using-superset/version-history.mdx` (section "Who sees the history") and the new bullet under `## Next` in `UPDATING.md`. 2. Optional behaviour check: with `VERSIONED_ENTITIES` capture on, create a chart via the API with legacy params (`granularity_sqla`, `time_range`), make one edit in Explore and save — the history shows the edit plus a single migration entry; a second edit records only the edit. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Migration is atomic, supports rollback & is backwards-compatible - [ ] Confirm DB migration upgrade and downgrade tested - [ ] Runtime estimates and downtime expectations provided - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01JRLEJS4mUqKBoPjSjviKUW -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
