Skip to content

fix: remove stale Shipyard Neo core config connectivity warning #8602

@zouyonghe

Description

@zouyonghe

What to build

Remove or update the core dashboard config-save Shipyard Neo connectivity warning now that concrete sandbox runtimes have been extracted into sandbox provider plugins. Core config save should not inspect removed provider-specific keys such as shipyard_neo_endpoint or shipyard_neo_access_token.

Acceptance criteria

  • Saving core config with sandbox booter set to a provider id does not read removed Shipyard Neo core config keys.
  • Provider-specific connectivity validation, if still needed, lives with the provider/plugin configuration path.
  • Existing tests that assert the old warning are removed or replaced with provider/plugin-scoped coverage.
  • Config save messaging no longer shows misleading Bay/Shipyard Neo warnings for plugin-managed providers.

Blocked by

None - can start immediately

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:coreThe bug / feature is about astrbot's core, backend

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions