Skip to content

[backport] #1193: [deps] Bump morgan from 1.11.0 to 1.12.0 (to 1.3) - #1253

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

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

Conversation

@openwisp-companion

Copy link
Copy Markdown

Backport of #1193 to 1.3.

Bumps [morgan](https://github.com/expressjs/morgan) from 1.11.0 to 1.12.0.
- [Release notes](https://github.com/expressjs/morgan/releases)
- [Changelog](https://github.com/expressjs/morgan/blob/master/HISTORY.md)
- [Commits](expressjs/morgan@1.11.0...1.12.0)

---
updated-dependencies:
- dependency-name: morgan
  dependency-version: 1.12.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
(cherry picked from commit 29de286)
@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: 1caf4345-3fb9-4e50-86dc-6ca8fe650f21

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 and Jest

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

  • Test Failures: Multiple Selenium browser test suites failed (mobile-phone-change.test.js, mobile-verfication.test.js, and cross-org-phone-verification.test.js) due to timeout issues, undefined elements (isDisplayed), missing toast error messages ("Invalid code."), and unexpected URL redirections.
  • Fix: Review the UI logic and Selenium selectors in these tests to ensure elements are correctly rendered, loaded, and visible before assertions or interactions are performed. Run the tests locally using yarn browser-test to debug timing and rendering inconsistencies.

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