This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/github_actions/actions/setup-node-6.3.0
in repository https://gitbox.apache.org/repos/asf/fineract.git
omit fb7259a130 Bump actions/setup-node from 4.4.0 to 6.3.0
add 9a1113496b FINERACT-2500: Update cucumber docs. Add require tenant
header for business-date API, enforce test profile for E2E
add 2a68ae9a51 Bump actions/setup-node from 4.4.0 to 6.3.0
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 (fb7259a130)
\
N -- N -- N
refs/heads/dependabot/github_actions/actions/setup-node-6.3.0 (2a68ae9a51)
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:
fineract-doc/src/docs/en/chapters/testing/cucumber.adoc | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
