diff --git a/BuildInfo_8cpp_source.html b/BuildInfo_8cpp_source.html index a1634f3f18..1a332a3d30 100644 --- a/BuildInfo_8cpp_source.html +++ b/BuildInfo_8cpp_source.html @@ -104,7 +104,7 @@ $(function() {
- + diff --git a/md____w_rippled_rippled_RELEASENOTES.html b/md____w_rippled_rippled_RELEASENOTES.html index 9c58f407e6..4054854dde 100644 --- a/md____w_rippled_rippled_RELEASENOTES.html +++ b/md____w_rippled_rippled_RELEASENOTES.html @@ -80,6 +80,40 @@ Change LogThis release introduces several new features including changes to the XRP Ledger's consensus mechanism to make it even more robust in adverse conditions, as well as numerous bug fixes and optimizations.
+rippled they are using, as well as the hash of the last ledger they consider to be fully validated, in validation messages. [#3291] HardenedValidations amendment is enabled and the validators begin reporting the versions of rippled they are running, a server can check how many of the validators on its UNL run a newer version of the software than itself. If more than 60% of a server's validators are running a newer version, the server writes a message to notify the operator to consider upgrading their software. [#3447][ips_fixed] and [ips] stanzas now use the IANA-assigned port for the XRP Ledger protocol (2459) when no port is specified. The connect API method also uses the same port by default. [#2861].ledger_cleaner command to rippled command line help [#3305]The rippled 1.5.0 release introduces several improvements and new features, including support for gRPC API, API versioning, UNL propagation via the peer network, new RPC methods validator_info and manifest, augmented submit method, improved tx method response, improved command line parsing, improved handshake protocol, improved package building and various other minor bug fixes and improvements.
This release also introduces two new amendments: fixQualityUpperBound and RequireFullyCanonicalSig.
Beast code. 172ead8226529d3e6fThe rippled 1.4.0 release introduces several improvements and new features, including support for deleting accounts, improved peer slot management, improved CI integration and package building and support for C++17 and Boost 1.71. Finally, this release removes the code for the SHAMapV2 amendment which failed to gain majority support and has been obsoleted by other improvements.
New and Updated Features
server_state when a server detects a disagreement between itself and the network.channel_authorize command.The rippled 1.3.1 release improves the built-in deadlock detection code, improves logging during process startup, changes the package build pipeline and improves the build documentation.
New and Updated Features
@@ -131,7 +165,7 @@ Version 1.3.1The rippled 1.3.0 release introduces several new features and overall improvements to the codebase, including the fixMasterKeyAsRegularKey amendment, code to adjust the timing of the consensus process and support for decentralized validator domain verification. The release also includes miscellaneous improvements including in the transaction censorship detection code, transaction validation code, manifest parsing code, configuration file parsing code, log file rotation code, and in the build, continuous integration, testing and package building pipelines.
New and Updated Features
The rippled 1.2.4 release improves the way that shard crawl requests are routed and the robustness of configured validator list retrieval by imposing a 20 second timeout.
New and Updated Features
@@ -153,7 +187,7 @@ Version 1.2.4The rippled 1.2.3 release corrects a technical flaw which in some circumstances can cause a null pointer dereference that can crash the server.
New and Updated Features
@@ -162,7 +196,7 @@ Version 1.2.3The rippled 1.2.2 release corrects a technical flaw in the fee escalation engine which could cause some fee metrics to be calculated incorrectly. In some circumstances this can potentially cause the server to crash.
New and Updated Features
@@ -171,7 +205,7 @@ Version 1.2.2The rippled 1.2.1 release introduces several fixes including a change in the information reported via the enhanced crawl functionality introduced in the 1.2.0 release, a fix for a potential race condition when processing a status change message for a peer, and for a technical flaw that could cause a server to not properly detect that it had lost all its peers.
The release also adds the delivered_amount field to more responses to simplify the handling of payment or check cashing transactions.
delivered_amount to more RPC commands (f2756914)The rippled 1.2.0 release introduces the MultisignReserve Amendment, which reduces the reserve requirement associated with signer lists. This release also includes incremental improvements to the code that handles offers. Furthermore, rippled now also has the ability to automatically detect transaction censorship attempts and issue warnings of increasing severity for transactions that should have been included in a closed ledger after several rounds of consensus.
New and Updated Features
@@ -212,7 +246,7 @@ Version 1.2.0The rippled 1.1.2 release introduces a fix for an issue that could have prevented cluster peers from successfully bypassing connection limits when connecting to other servers on the same cluster. Additionally, it improves logic used to determine what the preferred ledger is during suboptimal network conditions.
New and Updated Features
@@ -222,7 +256,7 @@ Version 1.1.2The rippled 1.1.1 release adds support for redirections when retrieving validator lists and changes the way that validators with an expired list behave. Additionally, informational commands return more useful information to allow server operators to determine the state of their server
New and Updated Features
@@ -234,7 +268,7 @@ Version 1.1.1The rippled 1.1.0 release release includes the DepositPreAuth amendment, which combined with the previously released DepositAuth amendment, allows users to pre-authorize incoming transactions to accounts, by whitelisting sender addresses. The 1.1.0 release also includes incremental improvements to several previously released features (fix1515 amendment), deprecates support for the sign and sign_for commands from the rippled API and improves invariant checking for enhanced security.
Ripple recommends that all server operators upgrade to XRP Ledger version 1.1.0 by Thursday, 2018-09-27, to ensure service continuity.
@@ -270,7 +304,7 @@ Version 1.1.0The rippled 1.0.0 release includes incremental improvements to several previously released features.
New and Updated Features
@@ -284,7 +318,7 @@ Version 1.0.0.check, escrow, and pay_chan to ledger_entry (RIPD-1600)The rippled 0.90.1 release includes fixes for issues reported by external security researchers. These issues, when exploited, could cause a rippled instance to restart or, in some circumstances, stop executing. While these issues can result in a denial of service attack, none affect the integrity of the XRP Ledger and no user funds, including XRP, are at risk.
New and Updated Features
@@ -300,7 +334,7 @@ Version 0.90.1The rippled 0.90.0 release introduces several features and enhancements that improve the reliability, scalability and security of the XRP Ledger.
Highlights of this release include:
@@ -343,7 +377,7 @@ Version 0.90.0The rippled 0.81.0 release introduces changes that improve the scalability of the XRP Ledger and transitions the recommended validator configuration to a new hosted site, as described in Ripple's Decentralization Strategy Update post.
New and Updated Features
@@ -354,7 +388,7 @@ Version 0.81.0The rippled 0.80.2 release introduces changes that improve the scalability of the XRP Ledger.
New and Updated Features
@@ -365,7 +399,7 @@ Version 0.80.2The rippled 0.80.1 release provides several enhancements in support of published validator lists and corrects several bugs.
New and Updated Features
@@ -382,7 +416,7 @@ Version 0.80.1The rippled 0.80.0 release introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger.
Highlights of this release include:
@@ -410,7 +444,7 @@ Version 0.80.0setAmendmentBlocked is only called when processing the EnableAmendment transaction for the amendment (#2137)The rippled 0.70.2 release corrects an emergent behavior which causes large numbers of transactions to get stuck in different nodes' open ledgers without being passed on to validators, resulting in a spike in the open ledger fee on those nodes.
New and Updated Features
@@ -419,7 +453,7 @@ Version 0.70.2The rippled 0.70.1 release corrects a technical flaw in the newly refactored consensus code that could cause a node to get stuck in consensus due to stale votes from a peer, and allows compiling rippled under the 1.1.x releases of OpenSSL.
New and Updated Features
@@ -430,7 +464,7 @@ Version 0.70.1The rippled 0.70.0 release introduces several enhancements that improve the reliability, scalability and security of the network.
Highlights of this release include:
@@ -466,28 +500,28 @@ Version 0.70.0The rippled 0.60.3 release helps to increase the stability of the network under heavy load.
New and Updated Features
This release has no new features.
Bug Fixes
Server overlay improvements (#2110)
-The rippled 0.60.2 release further strengthens handling of cases associated with a previously patched exploit, in which NoRipple flags were being bypassed by using offers.
New and Updated Features
This release has no new features.
Bug Fixes
Prevent the ability to bypass the NoRipple flag using offers (#7cd4d78)
The rippled 0.60.1 release corrects a technical flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values for Escrow and Payment Channel ledger entries. rippled version 0.60.1 also fixes a problem where the WebSocket timeout timer would not be cancelled when certain errors occurred during subscription streams. Ripple requires upgrading to rippled version 0.60.1 immediately.
New and Updated Feature
This release has no new features.
Bug Fixes
Correct calculation of Escrow and Payment Channel indices. Fix WebSocket timeout timer issues.
-The rippled 0.60.0 release introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL), including features that add ledger interoperability by improving Interledger Protocol compatibility. Ripple recommends that all server operators upgrade to version 0.60.0 by Thursday, 2017-03-30, for service continuity.
Highlights of this release include:
@@ -529,21 +563,21 @@ Version 0.60.0The rippled 0.50.3 release corrects a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the NoRipple flag. Ripple recommends that all server operators immediately upgrade to version 0.50.3.
New and Updated Features
This release has no new features.
Bug Fixes
Correct a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the “NoRipple” flag.
-The rippled 0.50.2 release adjusts the default TLS cipher list and corrects a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running rippled servers that accept client connections over TLS.
New and Updated Features
This release has no new features.
Bug Fixes
Adjust the default cipher list and correct a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword (#1985)
The rippled 0.50.0 release includes TickSize, which allows gateways to set a "tick size" for assets they issue to help promote faster price discovery and deeper liquidity, as well as reduce transaction spam and ledger churn on RCL. Ripple expects TickSize to be enabled via an Amendment called TickSize on Tuesday, 2017-02-21.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -596,7 +630,7 @@ Version 0.50.0We expect the previously announced Suspended Payments feature, which introduces new transaction types to the Ripple protocol that will permit users to cryptographically escrow XRP on RCL, to be enabled via the SusPay Amendment on Tuesday, 2017-02-21.
Also, we expect support for crypto-conditions, which are signature-like structures that can be used with suspended payments to support ILP integration, to be included in the next rippled release scheduled for March.
Lastly, we do not have an update on the previously announced changes to the hash tree structure that rippled uses to represent a ledger, called SHAMapV2. At the time of activation, this amendment will require brief scheduled allowable unavailability while the changes to the hash tree structure are computed by the network. We will keep the community updated as we progress towards this date (TBA).
-The rippled 0.40.1 release increases SQLite database limits in all rippled servers. Ripple recommends upgrading to 0.40.1 only if server operators are running rippled servers with full-history of the ledger. There are no new or updated features in the 0.40.1 release.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -604,7 +638,7 @@ Version 0.40.1This release has no new features.
Bug Fixes
Increase SQLite database limits to prevent full-history servers from crashing when restarting. (#1961)
-The rippled 0.40.0 release includes Suspended Payments, a new transaction type on the Ripple network that functions similar to an escrow service, which permits users cryptographically escrow XRP on RCL with an expiration date. Ripple expects Suspended Payments to be enabled via an Amendment named SusPay on Tuesday, 2017-01-17.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -619,7 +653,7 @@ Version 0.40.0Correct an issue in payment flow code that did not remove an unfunded offer (#1860)
Sign validator manifests with both ephemeral and master keys (#1865)
Correctly parse multi-buffer JSON messages (#1862)
-The rippled 0.33.0 release includes an improved version of the payment code, which we expect to be activated via Amendment on Wednesday, 2016-10-20 with the name Flow. We are also introducing XRP Payment Channels, a new structure in the ledger designed to support Interledger Protocol trust lines as balances get substantial, which we expect to be activated via Amendment on a future date (TBA) with the name PayChan. Lastly, we will be introducing changes to the hash tree structure that rippled uses to represent a ledger, which we expect to be available via Amendment on a future date (TBA) with the name SHAMapV2.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -644,7 +678,7 @@ Version 0.33.0PaymentSandbox::balanceHook can return the wrong issuer, which could cause the transfer fee to be incorrectly by-passed in rare circumstances. [RIPD-1274, #1827]
Prevent concurrent write operations in websockets [#1806]
Add HTTP status page for new websocket implementation [#1855]
-The rippled 0.32.1 release includes an improved version of the payment code, which we expect to be available via Amendment on Wednesday, 2016-08-24 with the name FlowV2, and a completely new implementation of the WebSocket protocol for serving clients.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -663,7 +697,7 @@ protocol = wss2Fix bug that could cause a previously fee queued transaction to not be relayed after being in the open ledger for an extended time without being included in a validated ledger. Fix bug that would allow an account to have more than the allowed limit of transactions in the fee queue. Fix bug that could crash debug builds in rare cases when replacing a dropped transaction. (RIPD-1200)
Remove incompatible OS X switches in Test.py (RIPD-1250)
Autofilling a transaction fee (sign / submit) with the experimental x-queue-okay parameter will use the user’s maximum fee if the open ledger fee is higher, improving queue position, and giving the tx more chance to succeed. (RIPD-1194)
The rippled 0.32.0 release improves transaction queue which now supports batching and can hold up to 10 transactions per account, allowing users to queue multiple transactions for processing when the network load is high. Additionally, the server_info and server_state commands now include information on transaction cost multipliers and the fee command is available to unprivileged users. We advise rippled operators to upgrade immediately.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -709,7 +743,7 @@ Version 0.32.0The rippled 0.31.2 release corrects issues with the fee escalation algorithm. We advise rippled operators to upgrade immediately.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -720,7 +754,7 @@ Version 0.31.2The rippled 0.31.1 release contains one important bug fix. We advise rippled operators to upgrade immediately.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum. For other platforms, please compile the new version from source.
@@ -731,7 +765,7 @@ Version 0.31.1LedgerSequence field. Previous versions of rippled incorrectly assumed that the optional validation field would always be included. Current versions of the software always include the field, and gracefully handle its absence.rippled 0.31.0 has been released.
You can update to the new version on Red Hat Enterprise Linux 7 or CentOS 7 using yum.
@@ -773,7 +807,7 @@ Version 0.31.0rippled 0.30.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.30.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit c717006c44126aa0edb3a36ca29ee30e7a72c1d3 @@ -832,7 +866,7 @@ Version 0.30.1
rippled 0.30.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.30.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit a8859b495b552fe1eb140771f0f2cb32d11d2ac2 @@ -881,7 +915,7 @@ Version 0.30.0
rippled 0.29.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/0.29.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 5964710f736e258c7892e8b848c48952a4c7856c @@ -931,7 +965,7 @@ Version 0.29.0
rippled 0.28.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/commits/release
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 6374aad9bc94595e051a04e23580617bc1aaf300 @@ -978,7 +1012,7 @@ Version 0.28.2
rippled 0.28.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 399c43cae6e90a428e9ce6a988123972b0f03c99 @@ -1028,7 +1062,7 @@ Version 0.28.1
rippled 0.28.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.28.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 7efd0ab0d6ef017331a0e214a3053893c88f38a9 @@ -1120,7 +1154,7 @@ Version 0.28.0
rippled 0.27.4 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.4
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 92812fe7239ffa3ba91649b2ece1e892b866ec2a @@ -1146,7 +1180,7 @@ Version 0.27.4
rippled 0.27.3-sp2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit f999839e599e131ed624330ad0ce85bb995f02d3 @@ -1172,7 +1206,7 @@ Version 0.27.3-sp2
rippled 0.27.3-sp1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3-sp1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 232693419a2c9a8276a0fae991f688f6f01a3add @@ -1198,7 +1232,7 @@ Version 0.27.3-sp1
rippled 0.27.3 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.3
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 70c2854f7c8a28801a7ebc81dd62bf0d068188f0 @@ -1224,7 +1258,7 @@ Version 0.27.3
rippled 0.27.2 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9cc8eec773e8afc9c12a6aab4982deda80495cf1 @@ -1264,7 +1298,7 @@ Version 0.27.2
rippled 0.27.1 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 95973ba3e8b0bd28eeaa034da8b806faaf498d8a @@ -1307,7 +1341,7 @@ Version 0.27.1
rippled 0.27.0 has been released. The commit can be found on GitHub at: https://github.com/ripple/rippled/tree/0.27.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit c6c8e5d70c6fbde02cd946135a061aa77744396f @@ -1432,7 +1466,7 @@ Version 0.27.0
rippled 0.26.4 has been released. The repository tag is 0.26.4 and can be found on GitHub at: https://github.com/ripple/rippled/commits/0.26.4
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 05a04aa80192452475888479c84ff4b9b54e6ae7 @@ -1504,7 +1538,7 @@ Version 0.26.4
rippled 0.26.3-sp1 has been released. The repository tag is 0.26.3-sp1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.3-sp1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 2ad6f0a65e248b4f614d38d199a9d5d02f5aaed8 @@ -1563,7 +1597,7 @@ Version 0.26.3-sp1
rippled 0.26.2 has been released. The repository tag is 0.26.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit b9454e0f0ca8dbc23844a0520d49394e10d445b1 @@ -1599,7 +1633,7 @@ Version 0.26.2
rippled v0.26.1 has been released. The repository tag is 0.26.1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9a0e806f78300374e20070e2573755fbafdbfd03 @@ -1624,7 +1658,7 @@ Version 0.26.1
rippled v0.26.0 has been released. The repository tag is 0.26.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.26.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 9fa5e3987260e39dba322f218d39ac228a5b361b @@ -1665,7 +1699,7 @@ Version 0.26.0
rippled v0.25.2 has been released. The repository tag is 0.25.2 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.2
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit ddf68d464d74e1c76a0cfd100a08bc8e65b91fec @@ -1691,7 +1725,7 @@ Version 0.25.2
rippled v0.25.1 has been released. The repository tag is 0.25.1 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.1
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit b677cacb8ce0d4ef21f8c60112af1db51dce5bb4 @@ -1727,7 +1761,7 @@ Version 0.25.1
rippled version 0.25.0 has been released. The repository tag is 0.25.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.25.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 29d1d5f06261a93c5e94b4011c7675ff42443b7f @@ -1761,7 +1795,7 @@ Version 0.25.0
rippled version 0.24.0 has been released. The repository tag is 0.24.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.24.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 3eb1c7bd6f93e5d874192197f76571184338f702 @@ -1790,7 +1824,7 @@ Version 0.24.0
rippled version 0.23.0 has been released. The repository tag is 0.23.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.23.0
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 29a4f61551236f70865d46d6653da2e62de1c701 @@ -1830,7 +1864,7 @@ Version 0.23.0
rippled version 0.22.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at: https://github.com/ripple/rippled/tree/develop The tag is 0.22.0 and can be found on GitHub at: https://github.com/ripple/rippled/tree/0.22.0
This is a critical release affecting transaction processing. All partners should update immediately.
@@ -1887,7 +1921,7 @@ Version 0.22.0rippled version 0.21.0 has been released. This release is currently the tip of the develop/ branch and can be found on GitHub at 1. The tag is 0.21.0-rc2 and can be found on GitHub at 2.
This is a critical release. All partners should update immediately.
@@ -1974,7 +2008,7 @@ Date: Fri Jan 24 11:17:16 2014 -0800rippled version 0.20.1 has been released. This release is currently the tip of the develop branch and the tag is 0.20.1.
This is a critical release. All partners should update immediately.
@@ -2078,7 +2112,7 @@ file_size_mult=2rippled version 0.19 has now been released. This release is currently the tip of the release branch and the tag is 0.19.0.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 26783607157a8b96e6e754f71565f4eb0134efc1 @@ -2131,7 +2165,7 @@ file_size_mult=2
rippled version 0.16 has now been released. This release is currently the tip of the master branch and the tag is v0.16.0.
Prior to building, please confirm you have the correct source tree with the git log command. The first log entry should be the change setting the version:
commit 15ef43505473225af21bb7b575fb0b628d5e7f73 @@ -2179,7 +2213,7 @@ path=db/hashnodeIssues
None known
-+
Version 0.14
rippled version 0.14 has now been released. This release is currently the tip of the master branch and the tag is v0.12.0.
Prior to building, please confirm you have the correct source tree with the
git logcommand. The first log entry should be the change setting the version:commit b6d11c08d0245ee9bafbb97143f5d685dd2979fc @@ -2227,7 +2261,7 @@ path=db/hashnodeIssues
None known
-+
Version 0.12
rippled version 0.12 has now been released. This release is currently the tip of the master branch and can be found on GitHub. The tag is v0.12.0.
Prior to building, please confirm you have the correct source tree with the
git logcommand. The first log entry should be the change setting the version:commit d0a9da6f16f4083993e4b6c5728777ffebf80f3a diff --git a/namespaceripple_1_1BuildInfo.html b/namespaceripple_1_1BuildInfo.html index 525e4c61d3..d5517ac76c 100644 --- a/namespaceripple_1_1BuildInfo.html +++ b/namespaceripple_1_1BuildInfo.html @@ -99,7 +99,7 @@ Functions
Variables | |
| char const *const | versionString = "1.6.0-rc3" |
| char const *const | versionString = "1.6.0" |
| static constexpr std::uint64_t | implementationVersionIdentifier |
| char const* const ripple::BuildInfo::versionString = "1.6.0-rc3" | +char const* const ripple::BuildInfo::versionString = "1.6.0" |