Skip to content

Restore @_group_ in Defaults List package overrides #3535

Closed

Description

@omry

Defaults List @_group_ support was removed by #3341 during the Hydra 1.1 compatibility cleanup. This breaks a supported, documented Hydra 1.3 feature.

This is distinct from the deprecated # @package _group_ header. In a nested Defaults List, @_group_ targets the selected config's absolute default package, avoiding both the containing config's package and a hardcoded destination.

For example, with preprocess/v1.yaml and preprocess/v2.yaml available:

# config.yaml
defaults:
  - preprocess: v2
  - feature_extract: v2
# feature_extract/v2.yaml
defaults:
  - override /preprocess@_group_: v1

Expected: select preprocess/v1 under the root-level preprocess package.

On Hydra 1.4.0rc1, composition fails:

No earlier Group Default for 'preprocess@feature_extract._group_' exists to override.

Using @_global_.preprocess works, but duplicates the group-derived package explicitly. The failure and workaround were verified while reviewing discussion #2792, whose original @_group_ guidance was valid for Hydra 1.3.

Restore symbolic @_group_ expansion in Defaults List package overrides, with regression coverage for nested inclusion and overrides. Restore the corresponding documentation while preserving the removal of deprecated symbolic package headers.

Activity

  1. added this to the Hydra 1.4.0 milestone on Oct 11, 2026
  2. added 2 commits that reference this issue on Oct 11, 2026
    afd599e
    2089a9a
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions