@VincentTunru the current framework I'm using (WXT) allows building for Firefox too. I'm waiting for the Chrome Web Store review process first before stepping up on automating the build + submission process.

@hboon not my first 😬 Mine goes was way back to 2009. Last time I update an extension was in 2020 👴

The UI looks different now. APIs change a little but don't quite remember. I'm using WXT which could generate the extensions for Firefox and Edge too. Chrome Web Store review process state that it might take weeks(?!) 🤞

@xssfox actually not bad 😉

Medien: 1

@cheeaun Don't you need to share exactly the code needed to produce the submitted extension?

A repository can change, so presumably it's not reliable.

Then again, I would hope that they ensure that the code is actually the exact code used to generate the artefacts, and the only way to do that is to actually build it. And if they do that, then there should be no need to upload the artefacts themselves, and only make the source available.

Hi @cheeaun,
IMO open source requires source. That's why I add a tar.gz of exactly the current source to https://seppo.mro.name/downloads/ releases. In fact the source IS the release and has a binary for convenience. The release is not all history or tooling, but one snapshot. Sure you could cheat, but that's not how you build trust. And development tools like history (git) are a different story, too.

Focus, remove all unnecessary tooling and publish source. Feels good.

@cheeaun Yeah I always just download my repo as a zip file and give it to them

🎉 Looks like it's up on Chrome Web Store https://chromewebstore.google.com/detail/stakataka/mdekjccfminpcgmcpmjnfgimifhibagc

Overview section is very under-described. Seems like I can only update it on the next release.

Edge Add-ons: In Review
Firefox Add-ons: Awaiting Review

@cheeaun that’s what I did for better Tweetdeck back then. I also had to leave a set of instructions to reproduce the build as well but I don’t know if they still require that