chore: adds to CLI extension Store release page - #2437
chore: adds to CLI extension Store release page#2437somethings (lasomethingsomething) wants to merge 12 commits into
Conversation
Developer Docs healthcheckStatus: Completed with |
There was a problem hiding this comment.
Pull request overview
Expands the Shopware CLI documentation page for releasing extension versions to the Shopware Store, clarifying what shopware-cli account producer extension upload does, what happens after upload, and how CI pipelines should treat the review result polling behavior.
Changes:
- Updates the page title/H1 capitalization for consistency.
- Replaces the old high-level upload workflow list with a more detailed, step-by-step description (version handling, metadata push, review outcomes).
- Adds new sections explaining post-upload behavior (no separate “release” command) and CI behavior when waiting/polling for review results.
Suppressed comments (1)
products/tools/cli/shopware-account-commands/releasing-extension-to-shopware-store.md:55
- The docs quote an exact log message for the timeout case. Consider describing the behavior (waits up to a limit, then stops waiting and exits successfully) without hardcoding the literal log text, to avoid drift if the CLI message changes.
By default, the command waits 10 seconds and then polls the review result up to 10 times with a 15-second interval (roughly two and a half minutes in total). If the review has not finished by then, the command logs `Skipping waiting for code review result as it took too long` and exits successfully. A green pipeline does not by itself prove that the review passed. Check the result in the Account, or poll it in a later job.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
| 5. Reports results: Shows whether the code review passed or failed | ||
| 1. Reads name and version: Both are taken from the zip file, so the extension must already exist in your producer account | ||
| 2. Creates or reuses the version: Creates a new binary for that version, or updates the existing binary if that version was already uploaded and is not published yet | ||
| 3. Pushes metadata: Sends the German and English changelog entries and the list of compatible Shopware versions, derived from the Composer constraint in `composer.json` or `manifest.xml` |
There was a problem hiding this comment.
Pushes metadata: Sends the German and English changelog entries
Few paragraphs above we are writing:
Having a German changelog is optional.
Maybe we could adjust that sentence?
…on-to-shopware-store.md Co-authored-by: Tomasz Turkowski <81367845+tturkowski@users.noreply.github.com>
Summary
Gives more details to this CLI docs page.
Related links
Closes shopware/shopware-cli#1259.
Checklist
PageRefreferences where relevant..gitbook.yamlif pages were moved, renamed, or deleted..wordlist.txt(and sorted it) if spellcheck flags new legitimate terms.Notes