Rifa Achrinza

Hi @sam-github, could you rebase your PR against the latest copy of master? That way the CI pipeline can be triggered.

Apologies @SAMIBETTAYEB, I didn't realise that this PR was targeting 3.x instead of master. I'll cherry-pick the commits into new PRs.

Thanks, @SAMIBETTAYEB; Would you be able to point this PR to the master branch (v5.x)? Or is 3.x necessary? Based on what I can tell, 5.x supports both LB3 and...

Thanks, @SAMIBETTAYEB. If you're comfortable with performing this, could you please reset the branch against master, then cherry-pick the commit range you intend to submit? The commands should look similar...

JugglingDB documentation: https://1602.github.io/jugglingdb/#DOCUMENTATION

Thanks for the PR, @arsa-dev! Since this requires an update to `loopback-datasource-juggler` and is a breaking change due to the driver update, I've scheduled this to align with the May...

re Juggler: If you can open a PR to fix the issue, I'll help push it through and get it released as well.

I suspect it's because of these lines: https://github.com/loopbackio/loopback-connector-mongodb/blob/5936ba0cd74a2b7dd84bb0925e0a9636de4f5d85/setup.sh#L44 https://github.com/loopbackio/loopback-connector-mongodb/blob/5936ba0cd74a2b7dd84bb0925e0a9636de4f5d85/setup.sh#L49 The CI pipeline pins to v4.4: https://github.com/loopbackio/loopback-connector-mongodb/blob/5936ba0cd74a2b7dd84bb0925e0a9636de4f5d85/.github/workflows/continuous-integration.yaml#L25 Compare to `latest` which AFAIK points to `5.0.7`. Try changing the line in your...

Not sure why the coverage plummeted to zero, but the test runs themselves look ok.

Workflow triggered - Just a heads up, our workflow doesn't allow merging PRs with Merge Commits, so they'll need to be dropped and, if needed, replaced with a rebase instead.