Skip to content

A shared service used by several tasks of a process is rejected at compile time in 5.5: deprecate it instead, reject it in 6.0 #382

Closed

Description

@njoubert-cleverage

Backward compatibility break of 5.5 (#339).

Since 5.5, TaskLocatorCompilerPass throws an InvalidArgumentException when the container is compiled if a shared service is referenced by several tasks of the same process. This configuration worked without error in 5.4: all these tasks ran with the same instance, initialized with the options of each task in turn. The change is documented in UPGRADE.md and the fix is simple (shared: false), but rejecting a configuration that worked breaks the applications on a minor update: their container no longer compiles.

Fix in 5.6: trigger a deprecation naming the service, the tasks and the process instead of throwing; reject it in 6.0.

Found during the audit after the 5.5 release (audit-v4-post-release.md #219).

Activity

  1. added 5 commits that reference this issue on Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions