Publish to Chrome and Firefox app stores

[thomaspaulb]

• Make a new signed Firefox XPI release by updating the version and using this job
• Publish to Firefox Store by uploading to Mozilla
• Add a job that autogenerates the Chrome package
• Publish to Chrome Web store by uploading to Google

[thomaspaulb]

@KKamaa To generate the XPI you'll have to fix this error in the job:

Error: InvalidManifest: Could not read manifest.json file at src/manifest.json: Error: ENOENT: no such file or directory, open 'src/manifest.json'
InvalidManifest: Could not read manifest.json file at src/manifest.json: Error: ENOENT: no such file or directory, open 'src/manifest.json'
    at getValidatedManifest (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/util/manifest.js:21:11)
    at async defaultPackageCreator (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/cmd/build.js:104:20)
    at async build (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/cmd/build.js:191:18)
    at async WebExtAction.cmd_build (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/src/action.js:99:19)
    at async main (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/src/index.js:59:16)

Which is probably as simple as pointing the manifest to the right folder.

[KKamaa]

@KKamaa To generate the XPI you'll have to fix this error in the job:

Error: InvalidManifest: Could not read manifest.json file at src/manifest.json: Error: ENOENT: no such file or directory, open 'src/manifest.json'
InvalidManifest: Could not read manifest.json file at src/manifest.json: Error: ENOENT: no such file or directory, open 'src/manifest.json'
    at getValidatedManifest (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/util/manifest.js:21:11)
    at async defaultPackageCreator (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/cmd/build.js:104:20)
    at async build (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/node_modules/web-ext/lib/cmd/build.js:191:18)
    at async WebExtAction.cmd_build (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/src/action.js:99:19)
    at async main (file:///home/runner/work/_actions/kewisch/action-web-ext/v1/src/index.js:59:16)

Which is probably as simple as pointing the manifest to the right folder.

this was fixed, I think the other issue is AMO credentials with the JWT issuer error. GitHub secrets for AMO signing were wrong or mismatched: AMO_JWT_ISSUER and AMO_JWT_SECRET I manaully added it from the generate xpi via firefox developer Hub as see here https://github.com/Therp/odoo-timer/releases/tag/v1.13-rc2

[thomaspaulb]

@KKamaa Ok yes I think last year I only went as far as having a job that builds the XPI, but not one that signs it automatically - I think I signed it manually when I uploaded it in the Mozilla account.

However I see that you added also the sign job and so I did now generate and set the AMO_JWT_ISSUER and AMO_JWT_SECRET, maybe you can check if it's working.