webiny-v5-to-v6-migration

Replace the ContextPlugin with a v6 DI service: define an interface using createAbstraction, implement it in a class, export it via createImplementation, and register it in a createFeature container. Consumers receive the service through constructor injection instead of the context object.

Create a class implementing the corresponding EventHandler interface, such as EntryAfterCreateEventHandler, with a handle method receiving the event payload. Register it in a feature container and filter by model.modelId since handlers fire for all models.

GraphQLSchemaPlugin is replaced by GraphQLSchemaFactory in v6. Similarly, CmsModelPlugin becomes ModelFactory, createSecurityRolePlugin becomes RoleFactory, and StorageTransformPlugin becomes StorageTransform, all registered through the DI container.

No, v6 removes the pattern of attaching services to the context object. Services must be defined as abstractions and registered in the DI container via createFeature, then injected as constructor dependencies into consumers.

Common mistakes include creating one abstraction per operation instead of multi-method services, naming features by technical events rather than business capabilities, attaching services to context, and placing business logic directly inside event handlers instead of delegating to services.

In v6, the content.i18n permission no longer exists and locale codes are removed. The models field becomes an array of modelId strings and groups becomes an array of group slug strings, while endpoint permissions like cms.endpoint.read remain unchanged.