Created a GitHub Action to work with wxt for publishing Safari extensions to the App Store

[rxliuli]

After a whole afternoon wrestling with App Store signing and notarization, I finally managed to build and publish extensions to all versions of Chrome/Firefox/Edge/Safari to their respective stores using GitHub Actions. I also created a GitHub Actions workflow to work alongside the previously created wxt-module-safari-xcode npm package.
https://github.com/rxliuli/safari-webext-publish-action

Along the way, I discovered a bug in an older version of wxt publish-browser-extension that fails to correctly update the version number on the Chrome Web Store.
aklinker1/publish-browser-extension#63

Although the issue has been fixed in the newer version, the old project cannot be resolved by directly updating wxt — you'll need to use overrides to force the update, because wxt's dependency declarations are very loose.

wxt/packages/wxt/package.json

Line 54 in dbbe14d

"publish-browser-extension": "^2.3.0 || ^3.0.2 || ^4.0.5",

Here's a quick screenshot of the completed GitHub Action, along with how many secrets are required — Apple is absolutely insane.

[PatrykKuniczak]

@rxliuli That's some kind of tutorial/tip for troubleshooting, why are you opened this discussion.
What are you want to talk about?

You've posted part of this on discord, and what are you want to achive here?

[rxliuli]

Just wanted to post this here as well, since some people might not use Discord. Maybe I should choose different tags?

[PatrykKuniczak]

Just wanted to post this here as well, since some people might not use Discord. Maybe I should choose different tags?

Yeah for sure not everybody on our DC server, but i hope better idea is to add this to examples and then add new question in FAQ.