Skip to content

ci: bump nightly stand pin to xrpld 3.4.0~rc1+202609050006.e3c8996e-1 - #182

Merged
Platonenkov merged 1 commit into
devfrom
nightly-watch/3.4.0-rc1-202609050006.e3c8996e-1
Sep 7, 2026
Merged

ci: bump nightly stand pin to xrpld 3.4.0~rc1+202609050006.e3c8996e-1#182
Platonenkov merged 1 commit into
devfrom
nightly-watch/3.4.0-rc1-202609050006.e3c8996e-1

Conversation

@xrpl-release-watch

Copy link
Copy Markdown

Summary

Automated bump by the nightly-pin-watch workflow: the nightly stand was pinned to a build 26d old.

  • .ci-config/Dockerfile.nightly: 3.4.0~b0+202608111815.26cc683e-1 -> 3.4.0~rc1+202609050006.e3c8996e-1
  • .ci-config/rippled.batchv11.cfg: [features]/[amendments] regenerated from develop e3c8996e, the commit that build was made from

Amendment changes

Added:

LendingProtocolV1_1
fixCleanup3_5_0

Removed:


definitions.json vs the new build


A node-only field here means the SDK is behind develop and needs a follow-up; local-only entries are informational.

Verification

The stand was built and started from the new pin on the runner, and the AMM sentinel amendment came up enabled at genesis, so the regenerated config was accepted.

Why this matters: definitions-watch raises its stand from this pin, so a stale pin makes the weekly develop-drift check compare against the past.

@Platonenkov
Platonenkov added this pull request to the merge queue Sep 7, 2026
Merged via the queue into dev with commit f704087 Sep 7, 2026
3 checks passed
@Platonenkov
Platonenkov deleted the nightly-watch/3.4.0-rc1-202609050006.e3c8996e-1 branch September 7, 2026 14:18
Platonenkov added a commit that referenced this pull request Sep 7, 2026
…he nightly stand

TestIClosedEndedVault, gated on LendingProtocolV1_1: a closed-ended vault through
its three phases (deposit in subscription; tecEXPIRED / tecTOO_SOON in
investment; withdrawal in redemption), an open-ended vault carrying no VaultKind
on the ledger, and a VaultWithdraw to a deposit-authorized destination that is
tecNO_PERMISSION without CredentialIDs and succeeds with them.

The run caught a wrong constant: kMinInvestmentPeriod is 180 s since rippled
#8151, not the 60 s of the original #7921. ValidateVaultCreate, its unit test
and the docs now say three minutes.

Found on the same stand and left for a follow-up: under LendingProtocolV1_1
LoanBrokerSet refuses an open-ended vault, and the whole Loan integration suite
builds on open-ended ones - 18/18 of TestILoan fail there, identically on
untouched dev. The CI stand (3.3.0) is unaffected.

Verified on xrpld 3.4.0-rc1 (the #182 pin): TestIClosedEndedVault 3/3,
TestIVault and TestICredential 25/25; TestU 1290/1290.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant