You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by er...@apache.org on 2026/09/02 11:16:44 UTC

(cordova-serve) branch chore/update-which-dep updated (30dbdae -> 85185a4)

This is an automated email from the ASF dual-hosted git repository.

erisu pushed a change to branch chore/update-which-dep
in repository https://gitbox.apache.org/repos/asf/cordova-serve.git


 discard 30dbdae  chore: updated node engine requirement
 discard 4bceb63  chore(dep): update which to 7.0.0
    omit 7c1aaaa  chore: update package-lock with npm update
    omit 10788cd  chore(dep): update open to 11.0.2
    omit 9f43fe7  chore(dep): update express to 5.2.1
    omit d1e74d5  chore(dev-dep): update jasmine to 7.0.0
    omit 610f153  chore(dev-dep): update c8 to 12.0.0
    omit 59d1392  chore(dev-dep): update @cordova/eslint-config to 6.0.1
     add 85e7475  chore: update npm dependencies (#95)
     add d40c8c5  chore(dep): update which to 7.0.0
     add 85185a4  chore: updated node engine requirement

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (30dbdae)
            \
             N -- N -- N   refs/heads/chore/update-which-dep (85185a4)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org