Skip to content

Fix regression in package.yml metadata.owner key#85

Merged
dkisselev merged 1 commit intomainfrom
push-qoonoyqpvuwm
Feb 26, 2026
Merged

Fix regression in package.yml metadata.owner key#85
dkisselev merged 1 commit intomainfrom
push-qoonoyqpvuwm

Conversation

@martinemde
Copy link
Contributor

As far as I can tell, this key was not intentionally removed and its presence is missed. Based on issues reported, We're restoring support rather than fix all the other things that depend on it.

Related to: rubyatscale/code_ownership#141

Copy link

@ivy ivy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gave rubyatscale/code_ownership#141 a read. Interesting! I would also prefer a single way to do this but that's easier said than done. 😓

As far as I can tell, this key was not intentionally removed and its
presence is missed. Based on issues reported, We're restoring support
rather than fix all the other things that depend on it.

Tolerate having both keys set as long as they are the same.
Fail when metadata.owner and owner are different.

Since we don't know what other tooling reads this owner key, it seems
better to error on ambiguity. It's possible other tooling reads this
value from the package.yml. We can adjust if we find problems.

Related to: rubyatscale/code_ownership#141
@dkisselev dkisselev merged commit 373eaca into main Feb 26, 2026
8 checks passed
@github-project-automation github-project-automation bot moved this from Triage to Done in Modularity Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants