workspace_config 1.0.0-beta1

First release of Workspace Config. It stages configuration changes in a workspace, the same way as content, and publishes them to Live together with the content that needs them.

Requirements

• Drupal 11.4 or later, with the core Workspaces module.
• Optional: Workspaces Extra (WSE) 3.0.0-alpha6 or later, to revert a published workspace, configuration included.
• Optional: Workspace Menu, to change menu links inside a workspace.

What stages

• Content types, fields and field storages, form and view displays, display modes, views, blocks, menus, text formats and editors, date formats, actions, comment types, REST resources and languages.
• More than 20 core settings objects, such as the site information, theme, performance, date, user and Views settings. A few keys stay Live-only, for example the site timezone.
• Configuration translations, language negotiation and language types.
• From contributed modules: Canvas, contact forms and Pathauto patterns.
• Pages that come from staged config, such as a new page view, work inside the workspace before publishing.

Keeping Live safe

• Configuration that is not marked as stageable can't be changed inside a workspace. Its forms only save in Live.
• Publishing imports the staged configuration with the full config import validation. If the import or the content publish fails, the Live configuration is rolled back and the workspace keeps its changes.
• Publishing logs a warning for configuration that Live changed after the workspace started staging it.

For module developers

• Make your configuration stageable with the WorkspaceSafe or WorkspaceIgnored schema constraints, or with hook_workspace_config_safe_list_alter() and hook_workspace_config_ignored_list_alter().
• Keep single keys in Live with the ConfigLiveOnlyKeys constraint.
• Tag services that cache configuration with workspace_config.reset, so they are reset on a workspace switch.

See Making your config stageable.

Known limitations

The full list is in Limitations.