mikebridge opened a new pull request, #45906:
URL: https://github.com/apache/superset/pull/45906

   ### SUMMARY
   
   TL;DR: Define which `apache-superset-core` imports semantic providers and 
host extensions can rely on, and how package versions and deprecations will be 
communicated before the next release.
   
   Background: The Python core package mixes provider contracts and host-bound 
persistence interfaces. Its dependency guide described the whole package as 
stable without naming the supported imports, and its package changelog did not 
record releases.
   
   Problem: Extension authors could treat incidental module names as supported 
API. The current package changelog also gave no guidance for upcoming contract 
changes and deprecations.
   
   Changes: Document the provider-facing import paths and symbols separately 
from host-extension models and DAOs; state that the host supplies `REQUEST` and 
`BACKGROUND` origins while explicit MCP, async and export binders are deferred; 
identify the reserved credentials channel and `CONFIG` origin; state the 
pre-1.0 version and deprecation policy; add an unreleased `0.2.0` package 
changelog entry and point `pyproject.toml` to that changelog. The installed 
package version stays at `0.1.0` until the coordinated core-package release 
bump. This PR changes documentation and package metadata only. Runtime export 
declarations follow after the provider boundary work lands.
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   
   Not applicable; no UI change.
   
   ### TESTING INSTRUCTIONS
   
   Review the `apache-superset-core` version and changelog URL in 
`superset-core/pyproject.toml`, then check the unreleased package changelog 
entry and the extension dependency guide. Confirm that the listed provider 
symbols exist in their named modules and that the origin wording matches the 
host's request/background inference. Changed-file pre-commit and 
metadata/symbol checks passed locally.
   
   ### 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
   
   The `0.2.0` changelog entry is marked unreleased; this PR does not publish a 
distribution or change runtime imports.
   


-- 
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]

Reply via email to