This is an automated email from the ASF dual-hosted git repository.
jan pushed a change to branch revert-docs-only
in repository https://gitbox.apache.org/repos/asf/pouchdb.git
discard e1bc30aca Revert "ci: only run tests for non-docs changes"
discard cc7415877 Revert "ci: update paths to ignore for tests"
discard bee028051 Revert "ci: update paths of doc changes"
add f8a2f1061 chore(deps-dev): bump handlebars from 4.7.8 to 4.7.9 (#9208)
add 45609f6cc chore(deps-dev): bump lodash from 4.17.23 to 4.18.1 (#9216)
add dc7f8f4d5 Revert "ci: update paths of doc changes"
add 07c9e5a25 Revert "ci: update paths to ignore for tests"
add 9f7fb209c Revert "ci: only run tests for non-docs changes"
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 (e1bc30aca)
\
N -- N -- N refs/heads/revert-docs-only (9f7fb209c)
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:
package-lock.json | 15 ++++++++-------
package.json | 2 +-
2 files changed, 9 insertions(+), 8 deletions(-)
