Meta: Attach built extension to releases

[mowies]

This PR

• attaches the distribution folder created by npm test to the created release
• archives the distribution folder into a tarball before attaching to the release

Closes #4595

[yakov116]

Not by a computer to test. Are you attaching the refined-github.zip file to the release?

[mowies]

@yakov116 Nope, I'm just attaching whatever gets generated by npm test into the distribution/ folder as a tar.gz archive.
That's what was asked for in the issue here: #4595

[yakov116]

@yakov116 Nope, I'm just attaching whatever gets generated by npm test into the distribution/ folder as a tar.gz archive.
That's what was asked for in the issue here: #4595

I think there is a misunderstanding.

We need the refined-github.zip as a separate attachment.

[mowies]

Could you please be more specific? I didn't find a zip archive that's generated somewhere already. I suppose you mean that the bundle files in distribution get zipped into refined-github.zip?

[fregante]

I think this is right already, what's the issue? The filename?

[yakov116]

I think this is right already, what's the issue? The filename?

I think so

[mowies]

Sure, I can change it to a zip with your mentioned name @yakov116

[fregante]

Thank you @mowies! Looking forward to more PRs like this

[fregante]

It worked (after a quick fix) but manifest.json had the version set to 0.0.0 😕 I removed the attachment:

refined-github-local-install.zip

[fregante]

I opened #6114 but I don't have time to test it right now. Feel free to try and open a new PR based on it if you'd like