klesh opened a new pull request, #9259: URL: https://github.com/apache/devlake/pull/9259
## Summary Reverts #9097, which added the Phase 1 deprecation warnings for the Python plugin framework (PyDevLake). This removes: - **`backend/python/README.md`** — DEPRECATED banner + migration guidance. - **`backend/python/plugins/azuredevops/README.md`** — deprecation notice pointing at `azuredevops_go`. - **`backend/core/runner/loader.go`** — one-time `WARN` log emitted at startup when remote (Python) plugins are loaded. - **`backend/core/plugin/plugin_meta.go`** — the `PluginDeprecation` interface. - **`backend/server/services/remote/plugin/plugin_impl.go`** — `DeprecationMessage()` on `remotePluginImpl`. - **`backend/server/api/plugininfo/plugininifo.go`** — the `deprecated` boolean on `GET /plugins`. - **config-ui** — `isDeprecated` / `deprecationMessage` on `IPluginConfig`, the flag on the Python `azuredevops` plugin config, and the "Deprecated" badge/alert rendering in the Connections page. ## Conflict resolution Later commits touched the same files, so two conflicts were resolved by hand: - `config-ui/src/plugins/register/azure/config.tsx` — dropped the `isDeprecated` / `deprecationMessage` fields. - `config-ui/src/routes/connection/styled.ts` — dropped the `& > .deprecated` badge style. Additionally, #9144 (`fix(config-ui) - for plugin deprecation notice`) added a `DeprecationAlert` banner and its usage on top of the code being reverted. That block referenced the removed types, so it is removed here too, together with the now-unused `DeprecationAlert` styled component and the `Alert` / `WarningOutlined` imports. ## Verification - `go build ./core/... ./server/...` — passes - `go vet` on the touched backend packages — passes - `npx tsc --noEmit` in `config-ui` — passes - `npx vitest run` in `config-ui` — 9 files / 65 tests pass Note: the Python plugin framework itself remains fully functional (as before); this only removes the deprecation notices. -- 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]
