(pulsar) branch lh-pip-478-followups updated (159ce2ad0987 -> 39b0be1bf1dc)

[lh...@apache.org]

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

lhotari pushed a change to branch lh-pip-478-followups
in repository https://gitbox.apache.org/repos/asf/pulsar.git


 discard 159ce2ad0987 [doc][misc] PIP-478: pin the shared-executor contract and the REFRESH sentinel delta
 discard d66149f989be [fix][client] PIP-478: stop handing plugins a null scheduler
 discard 6de22adb7d12 [feat][cli] PIP-478: add --jsse-provider / --jca-provider to the perf tools
 discard 2b8e00eed811 [feat][misc] PIP-478: give the JCA provider axis its configuration keys
 discard d72aff41bf25 [fix][misc] PIP-478: invalidate a rejected SASL role token, and pin the WebSocket proxy's outbound providers
 discard 1e1fa8e97a0b [improve][pip] PIP-478: correct five specification errors found reviewing the final state
 discard 49922d3d4a07 [fix][misc] PIP-478: second cross-review pass — builder reuse, purpose scoping, SASL token
 discard 1a1b189c722f [improve][misc] PIP-478: correct three javadocs describing the deleted v5→v4 adapter
 discard 3feaff12961c [fix][misc] PIP-478: whole-series cross-review fixes
 discard f23b53b1f0fe [improve][pip] PIP-478: reconcile the PIP with what was implemented
 discard c9d7b2d64ce4 [fix][misc] PIP-478: wire the provider keys and stop handing plugins a null executor
 discard aa811330681a [improve][misc] PIP-478: correct two comments that describe code that moved
 discard 70e1ff82d93b [improve][client] PIP-478: re-home the two invariants the v5->v4 adapter carried
 discard 9bb14fc0b060 [improve][client] PIP-478: move the binary auth driver out of the public API module
    omit be570cff9145 [improve][misc] PIP-478: cite the current hostname-verification standard
    omit 542bd1e0587e [improve][misc] PIP-478: qualify the CN fallback and correct two more fixture comments
    omit c4f505b900d6 [improve][misc] PIP-478: correct the RFC citation and finish the hostname sweep
    omit 004e2f11229b [improve][misc] PIP-478: finish correcting the hostname-verification record
    omit 13fb8956ef60 [improve][misc] PIP-478: remove the deprecated CN-based hostname matching
    omit e5d5db437734 [improve][misc] PIP-478: resolve BouncyCastle via JcaProviders and remove SecurityUtility
    omit b9a4cf394fc4 [improve][misc] PIP-478: remove the superseded PIP-337 PulsarSslFactory stack
     add 387e7c52b0e6 [improve][misc] PIP-478: remove the superseded PIP-337 TLS stack (#26322)
     add 9da0ed9d240e [improve][client] PIP-478: move the binary auth driver out of the public API module
     add a53269be371b [improve][client] PIP-478: re-home the two invariants the v5->v4 adapter carried
     add 455ff5581995 [improve][misc] PIP-478: correct two comments that describe code that moved
     add 3df1eff6e2b0 [fix][misc] PIP-478: wire the provider keys and stop handing plugins a null executor
     add 5833229f0631 [improve][pip] PIP-478: reconcile the PIP with what was implemented
     add c7db8c947439 [fix][misc] PIP-478: whole-series cross-review fixes
     add b9243d7958d3 [improve][misc] PIP-478: correct three javadocs describing the deleted v5→v4 adapter
     add c38c43ef00d9 [fix][misc] PIP-478: second cross-review pass — builder reuse, purpose scoping, SASL token
     add b0fdb31f797b [improve][pip] PIP-478: correct five specification errors found reviewing the final state
     add 0cb359567a4a [fix][misc] PIP-478: invalidate a rejected SASL role token, and pin the WebSocket proxy's outbound providers
     add 96bfbf5de415 [feat][misc] PIP-478: give the JCA provider axis its configuration keys
     add 857cc5f4d5ab [feat][cli] PIP-478: add --jsse-provider / --jca-provider to the perf tools
     add 4b13add1f46d [fix][client] PIP-478: stop handing plugins a null scheduler
     add 39b0be1bf1dc [doc][misc] PIP-478: pin the shared-executor contract and the REFRESH sentinel delta

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   (159ce2ad0987)
            \
             N -- N -- N   refs/heads/lh-pip-478-followups (39b0be1bf1dc)

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: