Native verified CRX uploads

[fregante]

https://developer.chrome.com/docs/webstore/update#protect-package-updates

chrome-webstore-upload users can already follow those steps and point ask the tool to upload the generated CRX. It would be cool to support it natively though.

Native support would be:

• add --pack-extension-key=privatekey.pem flag (matching chrome's)
• use google-chrome CLI command to pack the supplied folder instead of using zip

I'm unlikely to implement this anytime soon, but I'd accept a PR.

The constraints are:

• when the flag is provided, only folders are accepted as input, not zip files
• when the flag is provided, google-chrome must already be installed (I think it's there on GitHub actions)

[marcfbe]

This would be great to have. Things to consider:

• Repos or local developments often contain files or folders which should not be included in the zip/crx
• The pem file is a secret, obviously

[fregante]

Repos or local developments often contain files or folders which should not be included in the zip/crx

This package already doesn't concern itself with this. If you want to filter files out, you can create your own zip file first. In this case you'd have to move the files you want out of the folder.

[J3ekir]

chrome-webstore-upload users can already follow those steps and point ask the tool to upload the generated CRX. It would be cool to support it natively though.

What about the CLI version?

• when the flag is provided, google-chrome must already be installed (I think it's there on GitHub actions)

It is.

[J3ekir]

Can I provide a CRX file to the CLI version? Isn't it ZIP or a folder right now?

[J3ekir]

I don't think so.

This, calls this, call this because it doesn't end with .zip, calls this because it's a CRX file, not a folder that contains manifest.json.

[fregante]

It does now

v3.5.0 fregante/chrome-webstore-upload-cli#95

[fregante]

The command doesn't lend itself to be used this way because it creates files in the parent folder and won't let you choose. This means it would also need to take care of them (i.e. delete them), which is not safe.

For CLI users, the solution here will be:

google-chrome --pack-extension=my-folder --pack-extension-key=my-key.pem # must use the equal
chrome-webstore-upload --source my-folder.crx

Not worth merging the two calls.