Fix Chrome Web Store submission and Firefox release metadata for v2.7.0

[PeterDaveHello]

Summary

The v2.7.0 tagged release successfully built the release artifacts and submitted the extension to Firefox Add-ons and Microsoft Edge Add-ons, but the Chrome Web Store submission failed during OAuth authentication.

The Firefox extension submission itself succeeded, but the Firefox release metadata update did not run because the combined store submission command exited with an error after the Chrome failure.

Chrome Web Store

The tagged-release workflow failed while exchanging the configured Chrome Web Store refresh token for an access token:

[POST] "https://oauth2.googleapis.com/token": 400 Bad Request

{
  "error": "invalid_grant",
  "error_description": "Bad Request"
}

As a result, v2.7.0 was not submitted to the Chrome Web Store. The public Chrome Web Store listing is still on v2.6.1.

This most likely requires access to the Chrome Web Store publisher account and/or the OAuth credentials currently stored in the repository secrets.

@josStorer, could you please help check the Chrome Web Store credentials and either:

• regenerate/update the Chrome Web Store OAuth refresh token used by GitHub Actions, or
• manually submit chromium.zip from the v2.7.0 GitHub Release if refreshing the CI credential is not practical?

No credential values should be posted in this issue.

Firefox metadata

The Firefox package submission completed successfully:

[firefox] Submitting new version
Validation results: 0 errors, 27 warnings, 0 notices
✔ Firefox Addon Store

However, scripts/submit-stores.mjs only calls updateFirefoxVersionNotes() after the combined Chrome / Firefox / Edge submission command succeeds.

Since Chrome failed, publish-extension returned a non-zero exit code and the Firefox metadata update was skipped.

This means the v2.7.0 Firefox version may still have stale release notes and compatibility metadata even though the package itself was submitted successfully.

The repository already provides the dedicated Firefox metadata workflow, so v2.7.0 can be repaired independently by running:

Actions → Firefox metadata → Run workflow → version: 2.7.0

This does not resubmit the Firefox extension package.

Follow-up

Separately, the Firefox release-notes URL currently generated by the release script still points to the old josStorer/chatGPTBox repository namespace. That should be fixed independently so future metadata updates point directly to ChatGPTBox-dev/chatGPTBox.

Related release:
https://github.com/ChatGPTBox-dev/chatGPTBox/releases/tag/v2.7.0

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[josStorer]

I confirmed that the Chrome Web Store credentials have expired, and the existing publishing API will soon be deprecated. I think I'll re-adapt to the new publishing API and create new credentials in recent days.

[josStorer]

v2.7.0 has been reviewed and approved for release through manual submission

[PeterDaveHello]

Thanks! Let's see if it works in the next release!