(superset) branch fix/embedded-postmessage-origin-enforcement updated (859855bb93d -> fc39d278a77)

[ru...@apache.org]

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

rusackas pushed a change to branch fix/embedded-postmessage-origin-enforcement
in repository https://gitbox.apache.org/repos/asf/superset.git


    omit 859855bb93d Merge branch 'master' into fix/embedded-postmessage-origin-enforcement
    omit 0b3cc892aab fix(embedded): normalize allowed-domain origins and guard null message data
    omit 34921c11d4e test(embedded): assert allowed_domains via parsed bootstrap payload
    omit 669a3f850fd fix(embedded): enforce configured allowed domains for postMessage origin
     add 743f9011d9c fix(embedded): enforce configured allowed domains for postMessage origin
     add 7dbbfb16b82 test(embedded): assert allowed_domains via parsed bootstrap payload
     add fc39d278a77 fix(embedded): normalize allowed-domain origins and guard null message data

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   (859855bb93d)
            \
             N -- N -- N   refs/heads/fix/embedded-postmessage-origin-enforcement (fc39d278a77)

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: