Test trigger won't start when ledger connection not viable (digital-a…

…sset#6150)

changelog_begin
changelog_end

Fix issues cause by migration V25 and V26 (digital-asset#6107)

* Fix issues cause by migration V25 and V26

Fixes digital-asset#6017

Please note that migrating sandbox-classic from version 1.0.0 to 1.1.1 will cause
undefined behavior if the result is used to back a running ledger setup.

No migration should end at 1.1.1 and they should move past that until the version
that applies this fix to make sure the index database is in a consistent state.

Full write-up on the issue here: digital-asset#6017 (comment)

changelog_begin
[Sandbox Classic] Fix issue in migrating to version 1.1.1. If you did migrate to
version 1.1.1, do not use the resulting setup but make sure to migrate until this
version, which fixes the issue
See digital-asset#6017
changelog_end

* Add trailing newline

* Fix wrong hash for migration

* Address digital-asset#6107 (comment)

fix fat-jar publish (digital-asset#6046)

CHANGELOG_BEGIN
CHANGELOG_END

WIP: Draft version constraint generation (digital-asset#5472)

First version of static verification tool.

The current state of the tool: 
- Reads DAR files.
- Partially evaluates the code.
- Generates constraints for the field and choice to be verified.
- Passes the constraints to an SMT solver.
- Some basic tests.

Sandbox classic: Emulate legacy contract ID scheme (digital-asset#5929)



CHANGELOG_BEGIN
CHANGELOG_END

Always use the latest ledger config (digital-asset#5669)

CHANGELOG_BEGIN
- [Sandbox] The ledger API server will now always use the most recent ledger configuration.
  Until a ledger configuration is read from the ledger, command submissions will fail with the UNAVAILABLE error.
CHANGELOG_END

In kvutils, the first ledger configuration change needs
to have a generation one higher than the one returned
by getLedgerInitialConditions().

Remove initial config writing from sandbox as it's now written by the ledger API server

Always use the latest ledger config (digital-asset#5669)

CHANGELOG_BEGIN
- [Sandbox] The ledger API server will now always use the most recent ledger configuration.
  Until a ledger configuration is read from the ledger, command submissions will fail with the UNAVAILABLE error.
CHANGELOG_END

In kvutils, the first ledger configuration change needs
to have a generation one higher than the one returned
by getLedgerInitialConditions().

Remove initial config writing from sandbox as it's now written by the ledger API server

fix daml extension upload (digital-asset#5780)

With the current setup, we always push whatever version GitHub considers
as the latest, which is defined by date. This means that at the moment a
patch release could overwrite a less recent but higher-version release,
essentially downgrading the SDK to a previous, presumably less good user
experience.

This patches the upload process to choose the highest-numbered release
instead of the most recent one by date.

CHANGELOG_BEGIN
CHANGELOG_END

fix daml extension upload (digital-asset#5780)

With the current setup, we always push whatever version GitHub considers
as the latest, which is defined by date. This means that at the moment a
patch release could overwrite a less recent but higher-version release,
essentially downgrading the SDK to a previous, presumably less good user
experience.

This patches the upload process to choose the highest-numbered release
instead of the most recent one by date.

CHANGELOG_BEGIN
CHANGELOG_END

Backport "Remove duplicate ledger time field (digital-asset#5698)" (d…

…igital-asset#5713)

The duplicated information was not always in sync.

Fixes digital-asset#5662

CHANGELOG_BEGIN
- [Sandbox] Fix an issue where the sandbox would sometimes reject transactions
  with a "INVALID_ARGUMENT: Disputed" error if either of
  ``min_ledger_time_rel`` or ``min_ledger_time_abs`` was set in the
  submission request.
CHANGELOG_END

Co-authored-by: Robert Autenrieth <31539813+rautenrieth-da@users.noreply.github.com>