Upload plugin zips to GitHub releases
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 384
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 77
Description
Similar to #603 it would be great to offer the installable plugin zip for each release through GitHub) as well by attaching it to the Release for each tagged version.
Travis makes this rather easy using their Releases deployment provider:
https://docs.travis-ci.com/user/deployment/releases/
In addition to uploading the production build, we could also upload a development/debug version of the plugin which would be built using a development build. This would be very useful in support where error traces would contain the full names of component, reference accurate line numbers, etc.
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation Brief
Changelog entry
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing issue #603 and the Travis CI Releases deployment documentation linked in the issue. Trace how tagged releases produce the installable plugin zip, then verify that both production and development/debug artifacts are attached to each GitHub release with the expected version and build contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100