Code Browser

Completions API auth

[main] Flaky //daml-lf/snapshot:replay-benchmark-tests_test_suite_src_test_scala_com_digitalasset_daml_lf_testing_snapshot_ReplayBenchmarkIT.scala

add signature mechanism to dars

mv scala hardcoded stablepackageslist to generated

Further adopt feature versionranges scala side

[Error Message Improvement] error on missing key type signature

[Error Message Improvement] improve error on badly indented `choice`

Ensure benchmarking infrastructure and test runs can be launched in a simple manner

Uploading 3.4 dars to a 3.3 participant results in confusing dar validation errors

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

daml-script docker image should be created and published out of the `digital-asset/daml` repo

Ensure daml studio docs in 3.3 use --replace=always

Daml script compatibility test flakes with PACKAGE_SERVICE_CANNOT_AUTODETECT_SYNCHRONIZER

Add toString methods for TranslationFailed errors

Detect branch relevant for a release - only add `main` label when run on main

Generate LF versions based on bzl file

Remove TODOs to be done "after v2 becomes default"

Only require schema packages to be vetted

Efficient ListVettedPackages pagination

//script-runner-lib:script-runner-lib hardcodes canton version in error msg

//compiler/damlc/tests:data-dependencies: add cases for relevant lf versions

How do we control blast radius from bouncy castle upgrades

Enable compatibility tests between 3.4 and 3.3

Allow participants to ignore Dar Self-Consistency log warnings on dar file uploads

Ability for developers to create their own cryptographic hash functions

[3.4.0-13] Create SDK release

[3.4.0-12] Ensure that Canton Code drop is up to date

[3.4.0-05] Prepare SDK Release Notes

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

Go over test fixed in 2.2 release