Code Browser

Stage 2: determine sensible defaults for transaction limits

[test] Dummy flaky test issue for #23478, please ignore

daily-compat: Blackduck 'Open PR to update NOTICES file' fails with 'could not read Username' after long scans

daily-compat: update_canton fails when the canton snapshot is unchanged since the previous run (non-fast-forward push)

daily-compat: compat_versions_pr fails to queue builds (AZURE_DEVOPS_EXT_PAT not set)

add run-full-compat trailer to auto-generated compat versions PRs

Tag the commit author on Slack when a build fails on main

cross-sdk daml script: compatibility testing

Canton rejects LF 2.3 dars compiled after #23213

Daml-script tests can be run across SDK versions without recompiling

Pattern synonym support in data-dependencies

Generate daml-script stable-packages from LF so they do not change

Create mechanism for extensible stable types

Split fully stable types into separate packages

Separate daml-script into unstable and stable package

Make CallStack and SrcLoc types stable packages

TxConductor: Plug in engine in a parametric way

TxConductor: Handle exceptions

TxConductor: First implementation

Stage 1: post-processing validation and canton configuration

Gas: protect validating participants (SG-16)

Gas: protect submitting participant (SG-07)

Design + implementation of multi-package support

harmonization of dependencies and data dependencies

DAR file package ID checksum support

[2.10.5-11] Create SDK release

[2.10.5-10] Ensure that Canton Code drop is up to date

[2.10.5-05] Prepare SDK Release Notes

Write a grant proposal

[main] Flaky //compiler/damlc/tests:integration-v23