Releases: PrestaFlow/github-action
Releases · PrestaFlow/github-action
Release list
v2.1.0
Two additive Flashlight inputs — no behaviour change when omitted, full backward compat with v2.0.x.
New inputs
flashlight-mount('auto' | 'root' | 'modules' | 'themes', default'auto') — where to mount the workspace inside the Flashlight container.autokeeps the composer.json-based detection.rootmounts the workspace at/var/www/html:rw, matching Flashlight's owndevelop-prestashopexample — for custom PrestaShop builds.modules/themesforce those locations regardless of composer.json.
flashlight-init-scripts(path, default empty) — optional directory (absolute or relative to workspace) mounted read-only at/tmp/init-scripts. Flashlight runs every executable file with a shebang alphabetically, after MySQL dump restore and before nginx starts. Path is validated at parse time.
Upgrading
uses: PrestaFlow/github-action@v2— moving tag now points at v2.1.0.uses: PrestaFlow/github-action@v2.0.3— pin to@v2.1.0to opt in.
Also fixed
withInputstest helper: dashed input keys are now preserved when writing env vars (@actions/core.getInput('foo-bar')readsINPUT_FOO-BAR, notINPUT_FOO_BAR).
v2.0.3
Fixes
- fix(#7): write
.env.localwith PRESTAFLOW_FO_URL + PRESTAFLOW_PS_VERSION when Flashlight is on, so the PHP library picks up those vars via phpdotenv regardless of PHP's variables_order ($_ENV would otherwise remain empty in most CI setups). This is a client-side safety net — php-library v1.5.2 also handles this natively via a new Env helper. - fix(#7): skip API upload when there is no results.json to send. Previously the empty upload returned 453 and the exception bypassed the rest of the reporting flow (outputs left empty, no PR comment). Now: skip upload silently, still upload artifacts, still set outputs, still post the PR comment showing the zero-state gracefully.
Upgrading
uses: PrestaFlow/github-action@v2— moving tag now points at v2.0.3.uses: PrestaFlow/github-action@v2.0.2— pin to@v2.0.3to get the fixes.
v2.0.2
Bugfix release.
Fixes
- #5 fix(pr-comment): omit the 'View full report' link when
reportUrlis empty. Previously rendered[View full report]()which GitHub resolved to the current page (the PR). Backend to returnurlalongsideid— separate ticket. - #6 fix(flashlight): also export
PRESTAFLOW_PS_VERSION(in addition toPRESTAFLOW_FO_URL) when Flashlight is on, so the library'simportPage()picks the correct version-namespaced Page (Pages\\v9for PS 9.x, etc.) instead of defaulting to v8.
Upgrading
uses: PrestaFlow/github-action@v2— moving tag now points at v2.0.2, no workflow change required.uses: PrestaFlow/github-action@v2.0.1— pin to@v2.0.2to get the fixes.
v2.0.1
Bugfix release — validated end-to-end via github-action-smoke.
Fixes
- #2 fix(flashlight): export
PRESTAFLOW_FO_URL(with trailing slash) instead ofPRESTAFLOW_PS_URL. The PHP library readsPRESTAFLOW_FO_URL(and derives BO as${FO_URL}admin-dev/);PRESTAFLOW_PS_URLwas ignored. - #3 fix(runner): composer non-zero exit no longer swallows the reporting path. The library exits 1 whenever any test fails — that's its normal reporting channel. The action now logs a warning, keeps
stepFailed=true, and continues to parseresults.json, upload to the API + artifacts, set outputs, and post the PR comment. - #4 fix(flashlight): add MariaDB
mysqlsidecar (mariadb:lts) with the healthcheck the Flashlight docs prescribe, anddepends_on: condition: service_healthyon the PrestaShop service. BumpswaitFortimeout from 120s to 240s to cover cold-boot MySQL + PS install on GH Actions runners.
Upgrading
uses: PrestaFlow/github-action@v2— moving tag now points at v2.0.1 (no workflow change needed).uses: PrestaFlow/github-action@v2.0.0— pin to@v2.0.1to get the fixes.
v2.0.0
Full TypeScript rewrite of the action with new capabilities.
What's new
- Flashlight — set
flashlight: true+ps-version:to auto-provision a PrestaShop instance via Docker for tests to target. - Suite filtering —
suites: BackOffice,FrontOfficeto run only a subset (matrix-friendly). - PR comment — automatic PR summary (updated in place), with source location for failing tests.
- GitHub artifacts —
results.json+ error screenshots uploaded as a workflow artifact. - Rich outputs —
passed,failed,skipped,total,duration-ms,status,report-url(plus the existingid).
Backward compatibility
v1 workflows (token + projectId only) keep working unchanged.
Docs
Full reference: https://prestaflow.io/docs/library/1/digging-deeper/github-actions
Related PRs
- #1 — this rewrite
- PrestaFlow/php-library#50 — multi-suite envelope + source location (required)
- PrestaFlow/prestaflow.io#19 — docs update