ras-stack 0.17.0 → 0.18.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -381,6 +381,21 @@ release:
|
|
|
381
381
|
secrets: inherit
|
|
382
382
|
```
|
|
383
383
|
|
|
384
|
+
Browser jobs can cache the pinned Playwright payload through the shared setup action. Production-container E2E can use the reusable workflow, while repository-specific preparation and the actual test command remain inputs:
|
|
385
|
+
|
|
386
|
+
```yaml
|
|
387
|
+
e2e:
|
|
388
|
+
uses: richardsolomou/ras-stack/.github/workflows/check-container-browser.yml@v0.18.0
|
|
389
|
+
with:
|
|
390
|
+
image: my-app-e2e
|
|
391
|
+
cache-scope: my-app-e2e
|
|
392
|
+
prepare-command: just prepare-e2e
|
|
393
|
+
command: just e2e-run
|
|
394
|
+
just-version: '1.58.0'
|
|
395
|
+
```
|
|
396
|
+
|
|
397
|
+
The loaded image tag is also available to the command as `RAS_STACK_TEST_IMAGE`. Build and browser durations are written to the job summary, and failure artifacts remain configurable. Applications that need extra caches, services, registry publication, or a different PR/main topology can use `actions/build-container` and `actions/setup-playwright` inside their own job instead.
|
|
398
|
+
|
|
384
399
|
The workflow consumes pending changesets, commits the resulting versions and changelogs, pushes the commit and tag atomically, and creates a GitHub Release. It does nothing when no versioned changeset is present. The caller owns its checks, Changesets configuration, release policy, and any deployment that follows the release.
|
|
385
400
|
|
|
386
401
|
Pin actions and reusable workflows to a release tag and let Dependabot propose upgrades.
|