Automattic / Automattic/cortext
Prepare release automation
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 2
- Avg merge
- 3h 12m
- Merged PRs (30d)
- 8
Description
Cortext needs a release path we can run more than once without rebuilding the plan each time. This tracks release readiness for the first beta across GitHub, Playground, the desktop app, and WordPress.org.
- [x] Add milestone and type label automation. #276
- [x] Add plugin ZIP packaging. #279
- [x] Add the GitHub Release workflow. #282
- [ ] Prepare WordPress Playground publishing. #284
- [ ] Prepare desktop app packaging and distribution. #196
- [x] Set the plugin version metadata for `0.1.0`. #289
- [ ] Prepare WordPress.org publishing. #285
Contributor guide
Research direction
Start by reading the remaining work in #284, #196, and #285, alongside the completed release items #276, #279, #282, and #289. Determine how GitHub, Playground, the desktop app, and WordPress.org should form a repeatable first-beta release path, then verify each checklist item can be run without rebuilding the plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, wordpress
- Domain
- desktop-dev, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100