Skip to content

Releases: stellar/stellar-core

v18.0.0

27 Sep 23:22
e381447
Compare
Choose a tag to compare

Release notes:

This is a major release of stellar-core that implements “protocol 18”. Older versions will break as soon as the network gets upgraded to the latest version of the protocol.

Protocol 18 contains the following protocol changes:

Stability improvements

New features

Breaking changes

v18.0.0rc1

21 Sep 16:27
51e6e17
Compare
Choose a tag to compare
v18.0.0rc1 Pre-release
Pre-release

Release notes:

This is a major release of stellar-core that implements “protocol 18”.

Protocol 18 contains the following protocol changes:

Stability improvements

New features

Breaking changes

v17.4.0

30 Aug 19:31
c5f6349
Compare
Choose a tag to compare

Release notes:

Stability improvements

New features

None

Breaking changes

None

v17.4.0rc1

23 Aug 18:25
c5f6349
Compare
Choose a tag to compare
v17.4.0rc1 Pre-release
Pre-release

Release notes:

Stability improvements

New features

None

Breaking changes

None

v17.3.0

27 Jul 16:26
0b4c12a
Compare
Choose a tag to compare

Stability improvements

New features

Breaking changes

  • Store LedgerEntry in trustline table. Marked as a breaking change for visibility: no code or configuration needs to change, but on upgrade stellar-core will perform an automatic SQL schema migration, and will be unavailable to sync with its peers until this migration completes. On a fast SSD running on SQLite, the migration may be as quick as 2 minutes; on a slow spinning disk running on postgres it may take a half hour or more. Nodes should therefore be upgraded gradually and individually to avoid disruption.

v17.3.0rc1

21 Jul 19:28
0fc4ef8
Compare
Choose a tag to compare
v17.3.0rc1 Pre-release
Pre-release

Stability improvements

New features

Breaking changes

  • Store LedgerEntry in trustline table. Marked as a breaking change for visibility: no code or configuration needs to change, but on upgrade stellar-core will perform an automatic SQL schema migration, and will be unavailable to sync with its peers until this migration completes. On a fast SSD running on SQLite, the migration may be as quick as 2 minutes; on a slow spinning disk running on postgres it may take a half hour or more. Nodes should therefore be upgraded gradually and individually to avoid disruption.

v17.2.0

29 Jun 22:05
e47d483
Compare
Choose a tag to compare

v17.2.0rc2

24 Jun 18:23
e47d483
Compare
Choose a tag to compare

v17.2.0rc1

22 Jun 16:21
be75bd1
Compare
Choose a tag to compare

v17.1.0

24 May 19:03
fbc0325
Compare
Choose a tag to compare

This release makes several improvements to captive-core.

Stability improvements

New features

Breaking changes