Skip to content

[backport] #1194: [deps] Bump js-yaml from 4.3.1 to 4.3.2 (to 1.3) - #1254

Open
openwisp-companion[bot] wants to merge 1 commit into
1.3from
backport/1194-to-1.3-1794237836
Open

openwisp-companion[bot] wants to merge 1 commit into
1.3from
backport/1194-to-1.3-1794237836

Conversation

@openwisp-companion

Copy link
Copy Markdown

Backport of #1194 to 1.3.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.3.1 to 4.3.2.
- [Changelog](https://github.com/nodeca/js-yaml/blob/4.3.2/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.3.1...4.3.2)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.3.2
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 24fa75f)
@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one): 1

  • ai-review
🚫 Excluded labels (none allowed): 1

  • invalid

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 03354e29-33b6-47fb-9484-3873858eb634

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@openwisp-companion

Copy link
Copy Markdown
Author

The CI is failing due to transient infrastructure issues (not related to your code). I have restarted the failed jobs automatically (1/3).

@openwisp-companion

Copy link
Copy Markdown
Author

The CI is failing due to transient infrastructure issues (not related to your code). I have restarted the failed jobs automatically (2/3).

@openwisp-companion

Copy link
Copy Markdown
Author

The CI is failing due to transient infrastructure issues (not related to your code). I have restarted the failed jobs automatically (3/3).

@openwisp-companion

Copy link
Copy Markdown
Author

Browser Test Failures in Selenium Suites

Hello @app/openwisp-companion and @openwisp-companion[bot],
(Analysis for commit 438017a)

  • Test Failure: Multiple browser/Selenium tests failed due to timeouts or missing DOM elements (div#status, error toast messages, and URL navigation timeouts in mobile-phone-change.test.js, mobile-verfication.test.js, and cross-org-phone-verification.test.js).
  • Fix: Review the test assertions and element waits in these test files to ensure elements have fully rendered or adjust timeout thresholds if running in a resource-constrained environment. Fix the failing test logic and push a new commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants