The various services that make up the project (Cloudflare workers, GitHub actions) each have their own representation of the artifact metadata object (example here). However, the shape of this object is relatively standardized between service, with some deviations. The problem is that we're defining types to represent that object separately in each service, which is not DRY.
Those TypeScript data model types should ideally be defined in one place—probably the same repo as in #9—and then imported everywhere as git dependencies (a private npm registry is almost certainly unnecessary for this).
The various services that make up the project (Cloudflare workers, GitHub actions) each have their own representation of the artifact metadata object (example here). However, the shape of this object is relatively standardized between service, with some deviations. The problem is that we're defining types to represent that object separately in each service, which is not DRY.
Those TypeScript data model types should ideally be defined in one place—probably the same repo as in #9—and then imported everywhere as git dependencies (a private npm registry is almost certainly unnecessary for this).