Conversation
🦋 Changeset detectedLatest commit: 2b353fc The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Pull request overview
Updates the prepare-accounts composite GitHub Action used by the Playwright e2e workflows to avoid a sharded-workflow failure caused by masking the generated accounts payload.
Changes:
- Removes
::add-mask::${ACCOUNTS}from theprepare-accountsaction step. - Continues to pass the encrypted
ACCOUNTSvalue via$GITHUB_OUTPUTfor downstream jobs/steps.
| @@ -46,5 +46,4 @@ runs: | |||
| E2E_PERMISSIONS_USERS_PASSWORD: ${{ inputs.E2E_PERMISSIONS_USERS_PASSWORD }} | |||
| run: | | |||
| ACCOUNTS=$(node playwright/auth.js login) | |||
There was a problem hiding this comment.
Consider adding a short comment explaining why ACCOUNTS is intentionally not masked (GitHub Actions may refuse to set step/job outputs that contain masked values and will skip the output). This helps prevent accidental reintroduction of ::add-mask:: which can break sharded workflows again.
| ACCOUNTS=$(node playwright/auth.js login) | |
| ACCOUNTS=$(node playwright/auth.js login) | |
| # ACCOUNTS is intentionally not masked here; GitHub Actions may skip step/job outputs | |
| # that contain masked values, which would break consumers (including sharded workflows). |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6408 +/- ##
========================================
Coverage 43.13% 43.13%
========================================
Files 2524 2524
Lines 44009 44009
Branches 10011 10397 +386
========================================
Hits 18983 18983
Misses 24985 24985
Partials 41 41 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| "saleor-dashboard": patch | ||
| --- | ||
|
|
||
| `run pw-e2e` label on PRs will now also trigger a deployment. Previously e2e test failed due to a missing deployment without clear error. |
There was a problem hiding this comment.
Minor grammar: “Previously e2e test failed …” reads like a singular test; consider “Previously, e2e tests failed …” (or “the e2e suite failed …”) to match the meaning and improve clarity in the changelog.
| `run pw-e2e` label on PRs will now also trigger a deployment. Previously e2e test failed due to a missing deployment without clear error. | |
| `run pw-e2e` label on PRs will now also trigger a deployment. Previously, e2e tests failed due to a missing deployment without a clear error. |
| jobs: | ||
| initialize-cloud: | ||
| if: ${{ github.event_name == 'workflow_dispatch' || contains(github.event.pull_request.labels.*.name, 'test deployment') }} | ||
| if: ${{ github.event_name == 'workflow_dispatch' || contains(github.event.pull_request.labels.*.name, 'test deployment') || contains(github.event.pull_request.labels.*.name, 'run pw-e2e') }} |
There was a problem hiding this comment.
initialize-cloud now runs when a PR is labeled run pw-e2e, but unlike deploy-dashboard it doesn’t guard against fork PRs. On forks, required secrets (e.g. OP_SERVICE_ACCOUNT_TOKEN) won’t be available, so this job can fail unexpectedly if the label is applied. Consider adding the same github.event.pull_request.head.repo.full_name == 'saleor/saleor-dashboard' check (for pull_request events) to this job’s if: condition, while keeping workflow_dispatch working.
| if: ${{ github.event_name == 'workflow_dispatch' || contains(github.event.pull_request.labels.*.name, 'test deployment') || contains(github.event.pull_request.labels.*.name, 'run pw-e2e') }} | |
| if: ${{ github.event_name == 'workflow_dispatch' || (github.event_name == 'pull_request' && github.event.pull_request.head.repo.full_name == 'saleor/saleor-dashboard' && (contains(github.event.pull_request.labels.*.name, 'test deployment') || contains(github.event.pull_request.labels.*.name, 'run pw-e2e'))) }} |
| --- | ||
| "saleor-dashboard": patch | ||
| --- | ||
|
|
||
| Fixed main e2e test suite failing due to using masking on shared job output |
There was a problem hiding this comment.
This PR adds two separate changeset entries for the same underlying CI/workflow fix. That will produce two patch bumps / changelog entries; consider combining into a single changeset to avoid double version increments for one PR.
| "saleor-dashboard": patch | ||
| --- | ||
|
|
||
| Fixed main e2e test suite failing due to using masking on shared job output |
There was a problem hiding this comment.
I dont this this is actual product changelog. Same way we don't add changelog when we add tests
Fixed issue where masking caused sharded test workflow to break
This is not a security issue, it worked previously since it's already encrypted
e2e test now pass fine: https://github.com/saleor/saleor-dashboard/actions/runs/22908573370/job/66475269789?pr=6408
Fixed
run pw-e2efailing due to missing deployment (triggered by separate tag previously)