Bump arsenal to 8.4.11 (CRR reverted; unblocks 9.3)#6198
Conversation
Pick up arsenal 8.4.11, which reverts the multi-destination CRR changes (ARSN-600 / scality/Arsenal#2651) that were not backward-compatible for the 9.3 line. With CRR reverted, 9.3 consumes 8.4.x again with no code or test changes (full unit suite green). package.json pins the #8.4.11 version ref; yarn.lock resolves it to the ARSN-600 release commit so installs work before the 8.4.11 tag is published (same commit, nothing to change once tagged). Issue: CLDSRV-929
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
❌ 2 Tests Failed:
View the full list of 2 ❄️ flaky test(s)
To view more test analytics, go to the Test Analytics Dashboard |
SylvainSenechal
left a comment
There was a problem hiding this comment.
btw, why is it arsenal 8.4.11 and not 8.4.10 ? I think the messed up release is 8.4.9
I released a 8.4.10 with some other changes inbetween. |
|
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
This pull request does not target the following hotfix branch(es) so they
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-929. Goodbye delthas. |
What
Bump the arsenal dependency on
development/9.3from8.4.4to8.4.11.Why
8.4.11 reverts the multi-destination CRR changes (arsenal ARSN-600 / scality/Arsenal#2651) that were not backward-compatible for consumers still on the 8.4 line. With CRR reverted, 9.3 consumes 8.4.x again with no code or test changes — superseding the earlier "realign the replication tests" approach (closed PR #6193).
Verified locally against 8.4.11: full unit suite 5097 passing, 0 failing.
Pin detail
package.jsonpins the#8.4.11version ref. Since the tag isn't published yet,yarn.lockresolves it to the ARSN-600 release commit (5981b886) soyarn install --frozen-lockfileworks today; when arsenal tags 8.4.11 at that commit, nothing changes.Do not merge until arsenal 8.4.11 is released/tagged (ARSN-600 / scality/Arsenal#2651 merged). CRR continues on arsenal 8.5 → 9.4 moves to
8.5.0-preview.1on its waterfall branch.Issue: CLDSRV-929