fix: packageJsonStruct to allow repository.directory

[alber70g]

When releasing a package from a monorepo the repository.directory is used to identify which package is been released. This is used for the Github build provenance.

[Mrtenz]

Hi @alber70g, thanks for your PR! It looks like there's a lint issue:

Run yarn workspace @metamask/snaps-utils run lint:ci

/home/runner/work/snaps/snaps/packages/snaps-utils/src/types.ts
Error: 4:3 error 'object' is defined but never used @typescript-eslint/no-unused-vars

Happy to get this merged once you fixed that.

[alber70g]

When this is merged, how long will it take to be released on npm?

[Mrtenz]

When this is merged, how long will it take to be released on npm?

We're planning to do a release this week!

[barthuijgen]

Hi, I see this was released on 26 Sept, and we were able to update the build tooling to build our snap. But the Flask extension does not accept it yet. I've updated it to version 12.3.0-flask.0 but it gives a error installing our snap that repository.directory should be never.

Could you please look into publishing a new version of the extension with this change included? Thank you.

[Mrtenz]

Hi, I see this was released on 26 Sept, and we were able to update the build tooling to build our snap. But the Flask extension does not accept it yet. I've updated it to version 12.3.0-flask.0 but it gives a error installing our snap that repository.directory should be never.

Could you please look into publishing a new version of the extension with this change included? Thank you.

The updated version of snaps-utils is included in this PR: MetaMask/metamask-extension#27376. Unfortunately the extension is bound to a tight release schedule so it can take some weeks before this is included.