Skip to content

Add pre-publish validation that ensures shared tag manifests include all expected platforms defined by manifest.json #2127

@dagood

Description

@dagood

Currently, an official build might publish a partial manifest for a few reasons:

I can't think of a reason an official build should ever publish a shared tag that doesn't include all its platforms defined in the manifest.json. As far as I can tell, this always indicates a problem. To protect against regressions, it makes sense to me to explicitly check rather than relying on the logic along the way. Failing the build is vastly preferable to pushing out bad tags.

A dev build, on the other hand, might want to publish a shared tag that only includes some platforms, for avoiding waste, improving end-to-end performance, or some specific test. So, I imagine it'd have to be conditional, or simply opt-in.

Metadata

Metadata

Assignees

No fields configured for Feature.

Projects

Status
In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions