Propagate changes from main into development - #1269
Merged
Merged
Conversation
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Jeremy <jhatfield82@gmail.com>
The repo's default branch is development, but release-please-action defaults its target-branch input to the repository default branch via the API regardless of which branch the push trigger fired on. Since release-please-config.json/.release-please-manifest.json only exist on main (by design), the action was looking for them on development and failing with "Missing required manifest config."
Lets a human manually re-fire branch propagation (main -> development) when the workflow_run trigger doesn't fire on its own, without needing to re-run the upstream Docker Build workflow. The job's `if:` condition is extended to admit workflow_dispatch runs, since github.event.workflow_run is unset in that context.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…development # Conflicts: # .github/workflows/e2e-tests-split.yml
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
Contributor
✅ Supply Chain Verification Results✅ PASSED 📦 SBOM Summary
🔍 Vulnerability Scan
📎 Artifacts
Generated by Supply Chain Verification workflow • View Details |
navigateToLogin() in user-lifecycle.spec.ts had a single reload-based recovery attempt for Firefox's documented failure to produce a Playwright-trackable navigation-commit event (see docs/reports/qa_report_2026-07-26_shard4-reload-hang.md). Trace evidence from a fresh CI failure showed both the initial goto and the one reload attempt hitting this race in the same run, leaving the final toBeVisible() assertion hung on "waiting for navigation to finish" for its full 15s timeout with no further recovery. Wrap the goto/reload-then-check sequence in a bounded 3-attempt loop with short per-attempt timeouts on the non-final passes, so a stuck navigation fails fast into another reload instead of exhausting the only retry available. Verified locally: the previously-failing test passes 4/4 runs including under worker concurrency.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
developmentup withmain, bringing in the chain of CI reliability fixes from this session (Playwright install retry/timeout hardening, dpkg-lock cleanup, apt mirror tuning, WebKit-specific timeout budget fix) plus the release-please migration..github/workflows/e2e-tests-split.yml; resolved by takingmain's copy wholesale sincedevelopment's only unique change (a RenovateGO_VERSIONbump) was already present inmain's version.Test plan