digital-asset/daml
1
1
Fork 0
mirror of https://github.com/digital-asset/daml.git synced 2024-11-10 10:46:11 +03:00
Code Issues Projects Releases Wiki Activity
c327476da9
daml/release/artifacts.yaml

192 lines
6.7 KiB
YAML
Raw Normal View History

update copyright notices for 2021 (#8257) * update copyright notices for 2021 To be merged on 2021-01-01. CHANGELOG_BEGIN CHANGELOG_END * patch-bazel-windows & da-ghc-lib
2021-01-01 21:49:51 +03:00
# Copyright (c) 2021 Digital Asset (Switzerland) GmbH and/or its affiliates. All rights reserved.
add copyright headers to yml files (#4407) We seem to have forgotten about them in the copyright scripts. CHANGELOG_BEGIN CHANGELOG_END
2020-02-06 14:54:07 +03:00
# SPDX-License-Identifier: Apache-2.0
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //daml-assistant/scala-daml-project-config:scala-daml-project-config
Release missing sources jars (#2683) * Release missing sources jars * Review feedback by Gerolf
2019-08-29 09:21:57 +03:00
type: jar-scala
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_java
type: jar-proto
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_java
type: jar-proto
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/archive:daml_lf_1.8_archive_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/archive:daml_lf_1.8_archive_proto_java
type: jar-proto
LF: clone dev protobuf for LF 1.11 (#8373) Create protobuf packages for DAML-LF 1.11 This is part of #7139 CHANGELOG_BEGIN CHANGELOG_END
2021-01-06 16:32:26 +03:00
- target: //daml-lf/archive:daml_lf_1.11_archive_proto_jar
type: jar-lib
- target: //daml-lf/archive:daml_lf_1.11_archive_proto_java
type: jar-proto
LF: preview of LF 1.12 (#8652) CHANGELOG_BEGIN * LF: preview of LF 1.11. Preview versions can be changed only to include bug fixes. Changes of LF 1.12 include: - reduce transaction size by erasing type information in user-defined type. CHANGELOG_END
2021-01-28 19:28:41 +03:00
- target: //daml-lf/archive:daml_lf_1.12_archive_proto_jar
type: jar-lib
- target: //daml-lf/archive:daml_lf_1.12_archive_proto_java
type: jar-proto
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/archive:daml_lf_dev_archive_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/archive:daml_lf_dev_archive_proto_java
type: jar-proto
daml-lf: clean achive bazel build (#3175) * clean the mess in daml-lf achive bazel build * add release note * Address Moritz's comments * more release notes
2019-10-15 11:36:47 +03:00
- target: //daml-lf/archive:daml_lf_archive_reader
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //daml-lf/data:data
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
daml-lf: new data-scalacheck library for ImmArray, FrontStack, et al (#2342) * new data-scalacheck library for ImmArray, FrontStack, et al * add checkLaws functions as library to data-scalacheck * make checkLaws more configurable at use points
2019-08-01 18:10:56 +03:00
- target: //daml-lf/data-scalacheck:data-scalacheck
Release missing sources jars (#2683) * Release missing sources jars * Review feedback by Gerolf
2019-08-29 09:21:57 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //daml-lf/engine:engine
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/interface:interface
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //daml-lf/interpreter:interpreter
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //daml-lf/language:language
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //daml-lf/scenario-interpreter:scenario-interpreter
type: jar-scala
- target: //daml-lf/transaction:transaction
type: jar-scala
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/transaction:transaction_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/transaction:transaction_proto_java
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
type: jar-proto
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //daml-lf/transaction:value_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //daml-lf/transaction:value_proto_java
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
type: jar-proto
LF: rename library transaction-scalacheck to transaction-test-lib (#6347) * LF: rename library transaction-scalacheck to transaction-test-lib CHANGELOG_BEGIN CHANGELOG_END * move files in com/daml * missing change in release/artifacts.yaml * remove 'com/dam' from the path
2020-06-17 17:52:40 +03:00
- target: //daml-lf/transaction-test-lib:transaction-test-lib
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
type: jar-scala
- target: //daml-lf/validation:validation
type: jar-scala
interpret allowed updates and other actions in a free Trigger monad, like Script (#7456) * conservatively move daml-script, trigger SValue interpreters to common library * introduce expect and JavaList pattern for converters * clean up trigger Converter Command interpretation * add Church Free monad * add an action language for trigger updates * add expectE to remove some of the joins * convert more of the converters to expect * tool for unrolling Free/Roll * split handleStepResult up and clean up its pattern * handleStepFreeResult to interpret TriggerF * replace Free Church with Pure/Roll free from Script * newtype for ActionTrigger * replace update in low-level Trigger with Free TriggerF * submit one Commands at a time * boolean blindness strikes again * log missed TriggerF steps * comment actual Submit contents * match #7501 fromPureSExpr sig change in 00b80b8ea3 * avoid using forwardPort in runTrigger * push State back into DAML, so it can be excluded from the action list * push Message back into DAML, unifying the action language for initialState and update * bringing TriggerF into initial state * really add TriggerF into initial state, with all ports, tested * add ActionTrigger class, express initialState in its terms * add all TriggerF actions to existing TriggerA * Trigger.rule will no longer have Time argument * rename getS, setS to get, put, matching C.M.T.State from transformers * make high-level Rule evaluate to the underlying TriggerF sequence * Assert's testRule doesn't have a transform yet * move DamlTuple2 to common converter library - suggested by @cocreature; thanks * combine the two Frees, provide from Script * remove time argument from integration tests CHANGELOG_BEGIN - [Triggers] The ``Time`` argument was removed from the trigger rule function; instead, it can be fetched within the ``TriggerA`` ``do`` block by ``getTime``, as with ``Update`` and ``Scenario``. The ``LowLevel`` trigger interface has been redesigned; such triggers need to be rewritten or ported to high-level triggers. See `issue #7456 <https://github.com/digital-asset/daml/pull/7456>`_. CHANGELOG_END * add trigger rule simulator to support Assert module * missed new Free module - left in script per @cocreature * remove retract as we ended up using foldFree for that purpose instead - suggested by @cocreature; thanks * throw ConverterException instead of RuntimeException - suggested by @cocreature; thanks * remove Time argument from coin-upgrade-trigger * port trigger service tests * port trigger scenario test * put TriggerSetup and TriggerRule into LowLevel.Trigger instead of unboxed Free - suggested by @cocreature; thanks * remove Time argument from trigger compatibility test * submit commands as soon as each `emitCommands` is sequenced - we still collect a list, but only for tracking commandsInFlight * filter out compatibility tests for triggers before now * remove commented imports, libraries from new shared converter * make the TriggerF interpreter tail-recursive * remove unused compatibility trait * add back new state logging * remove refactoring comment * rewrite some LowLevel initialStates in do * hide Daml.Script.Free from docs Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org> * remove forwardPortInitialState - suggested by @cocreature; thanks * manually port low-level updates - suggested by @cocreature; thanks * remove forwardPort - suggested by @cocreature; thanks * fail faster on unrecognized TriggerF - suggested by @cocreature; thanks Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
2020-10-02 21:18:13 +03:00
- target: //daml-script/converter:converter
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //language-support/codegen-common:codegen-common
type: jar-scala
- target: //language-support/codegen-main:shaded_binary
Fix daml-sdk-head Maven install (#8962) * Fix daml-sdk-head Maven install There were two issues: 1. The generated pom.xml used to install everything in one step referenced the source files in the bazel directory rather than the released artifacts. This luckily worked so far but falls apart now since the 2.13 build overwrites the 2.12 build. Same issues that also blew up the actual release on Thursday. 2. Two artifacts are published as shaded jars. We treated those like Scala artifacts while they should be treated more like fat jars. They’re not quite like those since the file paths are different so I gave them a new release type. changelog_begin changelog_end * shut up hlint changelog_begin changelog_end * Fix broken comment for jarjar changelog_begin changelog_end
2021-02-26 23:20:04 +03:00
type: jar-jarjar
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //language-support/java/bindings:bindings-java
type: jar-lib
- target: //language-support/java/bindings-rxjava:bindings-rxjava
type: jar-lib
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //language-support/java/codegen:lib
type: jar-scala
- target: //language-support/java/codegen:shaded_binary
Fix daml-sdk-head Maven install (#8962) * Fix daml-sdk-head Maven install There were two issues: 1. The generated pom.xml used to install everything in one step referenced the source files in the bazel directory rather than the released artifacts. This luckily worked so far but falls apart now since the 2.13 build overwrites the 2.12 build. Same issues that also blew up the actual release on Thursday. 2. Two artifacts are published as shaded jars. We treated those like Scala artifacts while they should be treated more like fat jars. They’re not quite like those since the file paths are different so I gave them a new release type. changelog_begin changelog_end * shut up hlint changelog_begin changelog_end * Fix broken comment for jarjar changelog_begin changelog_end
2021-02-26 23:20:04 +03:00
type: jar-jarjar
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //language-support/scala/bindings:bindings
type: jar-scala
- target: //language-support/scala/bindings-akka:bindings-akka
type: jar-scala
- target: //language-support/scala/codegen:codegen
type: jar-scala
ledger-api: Use `proto_jars`, and publish Protobuf sources separately from the Scala classes. [KVL-714] (#8091) * ledger-api: Use `proto_jars`. CHANGELOG_BEGIN - [Ledger API] The Scala JARs containing the gRPC definitions no longer contain the *.proto files used to generate the ScalaPB-based classes. CHANGELOG_END * Create a source JAR for *.proto files in `proto_jars`. * ledger-api: Publish the protobuf sources as "ledger-api-proto". CHANGELOG_BEGIN - [Ledger API] The *.proto files containing the gRPC definitions are now provided by a new Maven Central artifact, with the group "com.daml" and the artifact name "ledger-api-proto". CHANGELOG_END * release: We don't need the "main-jar" option. * Bazel: Proto JARs will always have a Maven artifact suffix. * Bazel: Simplify Protobuf source file TAR and JAR targets. * Bazel: Extract out Protobuf functions.
2020-11-27 20:14:48 +03:00
- target: //ledger-api/grpc-definitions:ledger_api_proto_jar
type: jar-lib
- target: //ledger-api/grpc-definitions:ledger_api_proto_scala
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
- target: //ledger-api/rs-grpc-akka:rs-grpc-akka
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger-api/rs-grpc-bridge:rs-grpc-bridge
type: jar-lib
Ledger API: Add healthcheck endpoints. (#3573) * grpc-definitions: Delete health_service.proto We can use the version in io.grpc:grpc-services instead. * ledger: Delete ledger/API.md. * sandbox: Fix warnings in ApiServices flagged by IntelliJ. * sandbox: Implement a dummy grpc.health.v1.Health.Check endpoint. * sandbox: Implement a dummy grpc.health.v1.Health.Watch endpoint. * sandbox: Drop repeated elements from grpc.health.v1.Health.Watch. * sandbox: Wrap the HealthService in basic tests. * sandbox: Stop streaming the server health too. * ledger-api-test-tool: Health check tests. * Add a changelog entry for the health check endpoints. CHANGELOG_BEGIN - [Ledger API] Add healthcheck endpoints, conforming to the `GRPC Health Checking Protocol <https://github.com/grpc/grpc/blob/master/doc/health-checking.md>`_. It is always ``SERVING`` for now. - [DAML Ledger Integration Kit] Add conformance test coverage for the ``grpc.health.v1.Health`` service. CHANGELOG_END * ledger-api-integration-tests: Increment the number of services. * Apply suggestions from code review Co-Authored-By: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * sandbox: Use `AkkaBeforeAndAfterAll` in the HealthServiceSpec. In an attempt to get it working on CI. * sandbox: Change `dropRepeated` to `DropRepeated()`. Keep it in one file. * test-common: Use `Delayed.by` in `TimeBoundObserver`. * test-common: Close the source when `TimeBoundObserver` completes. * ./fmt.sh That'll teach me not to `--no-verify` just because it's a merge commit. * sandbox: Inline `HealthService.suppress`. At some point it was being used twice. * sandbox: Increase the timeout for HealthServiceSpec. * sandbox: Reimplement HealthService using the Scala protobuf types. * sandbox: Generate an Akka-compatible trait for the health service. And refactor a lot of test code to make it easy to test. * ledger-api-common: Move the HealthService here. * rs-grpc-testing-utils: Publish to Maven. * rs-grpc-testing-utils: Add Maven coordinates.
2019-11-22 17:02:05 +03:00
- target: //ledger-api/rs-grpc-testing-utils:rs-grpc-testing-utils
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger-api/testing-utils:testing-utils
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Integrate metrics for cache (#6043) * Integrate metrics for cache Centralizes the creation of instrumented caches in a single point and adds metrics coming from Caffeine into the mix. changelog_begin [Ledger API Server] if --max-state-value-cache-size is greater than zero, the following additional metrics will be recorded under the daml.kvutils.submission.validator.state_value_cache namespace: hits, misses, load_successes, load_failures, load_total_time, evictions and evicted_weight changelog_end * Fix Bazel build file formatting * Address https://github.com/digital-asset/daml/pull/6043#discussion_r427902339 * Address https://github.com/digital-asset/daml/pull/6043#discussion_r427904794 * Review DropwizardStatsCounter - address https://github.com/digital-asset/daml/pull/6043#discussion_r427905074 - address https://github.com/digital-asset/daml/pull/6043#discussion_r427905184 - address https://github.com/digital-asset/daml/pull/6043#discussion_r427905307 - address https://github.com/digital-asset/daml/pull/6043#discussion_r427905387 - address https://github.com/digital-asset/daml/pull/6043#discussion_r427905650 * Address https://github.com/digital-asset/daml/pull/6043#discussion_r427906243 * Fix implicit numeric widening fatal warning * Address https://github.com/digital-asset/daml/pull/6043#discussion_r427960762 * Fix infinite loop in metrics
2020-05-20 16:51:45 +03:00
- target: //ledger/caching:caching
type: jar-scala
Move common jwt cli flags (#7811) * move cliopts changelog_begin changelog_end * update artifacts.yaml Co-authored-by: Andreas Herrmann <andreas.herrmann@tweag.io>
2020-10-26 20:53:37 +03:00
- target: //ledger/cli-opts:cli-opts
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-akka:ledger-api-akka
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Move AuthService (#3272) * Move AuthService and Claims * Move interceptor and authorization wrappers * Add artifact * Address review comments
2019-10-29 18:46:43 +03:00
- target: //ledger/ledger-api-auth:ledger-api-auth
type: jar-scala
Add authentication to Java identity client (#3630) * Add authentication to Java identity client Contributes to #3626 No changelog added right now, it will be added with the PR that effectively closes the ticket. Moves `LedgerCallCredentials` to a shared package. Establishes the test framework for other Java clients. * Address https://github.com/digital-asset/daml/pull/3630#discussion_r350663731 * Address https://github.com/digital-asset/daml/pull/3630#discussion_r350663731 * Rebase and fix compilation errors * Fix type of jar in artifacts.yaml Co-Authored-By: Gerolf Seitz <gerolf.seitz@digitalasset.com> * Fix more errors emerged after rebase * Add dependency for DAML assistant ITs * Add missing dependency * Fix wrong dependency * fix release
2019-11-26 21:51:09 +03:00
- target: //ledger/ledger-api-auth-client:ledger-api-auth-client
type: jar-lib
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-client:ledger-api-client
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-common:ledger-api-common
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-domain:ledger-api-domain
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-health:ledger-api-health
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-api-test-tool:ledger-api-test-tool
Refactor and speed up release script (#431) This rewrites the release script to be a lot simpler and significantly faster: - The artifacts are now declared in a separate yaml file which should make it easier for people to modify and doesn’t clutter the actual code. - There is only a constant number of calls to Bazel which speeds up the script quite a bit. I verified that the release artifacts are the same that we got before and I traced the calls to the jfrog binary in a fake release and ignoring order they are identical.
2019-04-12 15:57:37 +03:00
type: jar-deploy
Publish ledger-on-memory (#7117) CHANGELOG_BEGIN - [Integration Kit] Publish package `com.daml:ledger-on-memory`. CHANGELOG_END
2020-08-13 15:32:04 +03:00
- target: //ledger/ledger-on-memory:ledger-on-memory
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger/ledger-on-sql:ledger-on-sql
Fixes #1204: Release bindings and codegens to Maven Central. (#1205) * Fixes #1204: Release bindings and codegens to Maven Central. Upload the Java and Scala Bindings with the respective code generator binaries to Sonatype Open Source Repository Host for synchronization with Maven Central.
2019-06-17 16:37:49 +03:00
type: jar-scala
resources: Customizable contexts. (#7678) * resources: Move builders into //ledger/ledger-resources. Keep the actual constructors in a trait, but instantiate it when working with ledger code. This allows us to later introduce an extra "context" type parameter to ResourceOwner. * resources-akka: Move the builders in to //ledger/ledger-resources. * resources: Introduce an abstract `Context` parameter for owners. This replaces the concrete `ExecutionContext`. While it _can_ be an execution context, it really doesn't matter as long as we can get at one somehow. This is being introduced so we can wrap the context in a container, either for type tagging or to include extra information. Because our current context _is_ `ExecutionContext`, and an implicit is provided to extract it, we can end up with two ways to get the same value. We use shadowing to prevent this. This problem should go away in the near future when a new context type is added. CHANGELOG_BEGIN - [Integration Kit] The `ResourceOwner` type is now parameterized by a `Context`, which is filled in by the corresponding `Context` class in the _ledger-resources_ dependency. This allows us to pass extra information through resource acquisition. CHANGELOG_END * ledger-resources: Move `ResourceOwner` here from `resources`. * ledger-resources: Remove dependencies from outside //ledger. * ledger-resource: Wrap the acquisition execution context in `Context`. So we can add a logging context to it. * resources: Pass the Context, not the ExecutionContext, to Resource. * Avoid importing `HasExecutionContext`. * ledger-resources: Publish to Maven Central. * resources: Make the small changes suggested by @stefanobaghino-da. Co-Authored-By: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com> * ledger-resources: Pull out a trait for test resource contexts. Saves a few lines of code. * Restore some imports that were accidentally wildcarded. * resources: Replace an `implicit def` with a couple of imports. * participant-integration-api: Simplify the JdbcLedgerDaoBackend tests. Try and use the right execution context where possible. Co-authored-by: Stefano Baghino <43749967+stefanobaghino-da@users.noreply.github.com>
2020-10-20 12:26:28 +03:00
- target: //ledger/ledger-resources:ledger-resources
type: jar-scala
ledger/metrics: Move metric helpers to their own Bazel package. (#5542) * ledger/metrics: Move metric helpers to their own Bazel package. CHANGELOG_BEGIN CHANGELOG_END * sandbox: Use ledger/metrics. * metrics: Rename `Metrics` to `Timed` and drop the `timed` prefix. Importing methods is harder than importing objects. * metrics: Publish to Maven Central.
2020-04-14 15:32:03 +03:00
- target: //ledger/metrics:metrics
type: jar-scala
Split sandbox code into separate packages (#6695) * Move public code into daml-integration-api CHANGELOG_BEGIN [DAML Integration Kit]: Removed sandbox specific code from the API intended to be used by ledger integrations. Use the maven coordinates ``com.daml:participant-integration-api:VERSION`` instead of ``com.daml:ledger-api-server`` or ``com.daml:sandbox``. CHANGELOG_END
2020-07-17 18:06:06 +03:00
- target: //ledger/participant-integration-api:ledger-api-server
type: jar-scala
- target: //ledger/participant-integration-api:participant-integration-api
type: jar-scala
Add damlonx artifacts to the release (#627)
2019-04-23 15:00:55 +03:00
- target: //ledger/participant-state:participant-state
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
kvutils: Publish the Protobuf definition. (#8098) CHANGELOG_BEGIN - [Integration Kit] The kvutils Protobuf definition is now published to Maven Central in a JAR, under the group "com.daml", with the artifact name "participant-state-kvutils-proto". CHANGELOG_END
2020-12-01 10:47:44 +03:00
- target: //ledger/participant-state/kvutils:daml_kvutils_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //ledger/participant-state/kvutils:daml_kvutils_proto_java
DamlOnX: release kvutils (#763) * Move package comment to correct place * Update kvutils package documentation * Release participant-state-kvutils
2019-04-29 17:05:22 +03:00
type: jar-proto
- target: //ledger/participant-state/kvutils:kvutils
Release scala source jars to bintray (#767) Tested with a dry run: Copying .../com_github_digital_asset_daml/bazel-out/k8-fastbuild/bin/ledger/api-server-damlonx/api-server-damlonx_src.jar to .../com/daml/ledger/api-server-damlonx_2.12/100.12.11/api-server-damlonx_2.12-100.12.11-sources.jar
2019-04-29 18:11:01 +03:00
type: jar-scala
Publish `com.daml.ledger:participant-state-kvutils-app` (#4480) CHANGELOG_BEGIN CHANGELOG_END
2020-02-12 11:45:52 +03:00
- target: //ledger/participant-state/kvutils/app:app
type: jar-scala
Refactor integrity checker into published "tools" lib + binary [KVL-557] (#7888) * Document new integrity checker options * Remove v2 from the bazel target in README * Refactor integrity checker into published "tools" lib + binary CHANGELOG_BEGIN CHANGELOG_END * Refine split * Release tools lib * Generalize IntegrityChecker.run * Use glob for test source definition * Widen glob for tools-tests to all (future) tool tests, not just integritycheck * Simplify test source globs * Simplify tools lib source glob * Fix build
2020-11-06 18:20:21 +03:00
- target: //ledger/participant-state/kvutils/tools:tools
type: jar-scala
When publishing Protobuf source JARs, publish the dependencies. (#8148) Previously, each Protobuf source JAR was considered independent, and did not require dependencies. This meant that the kvutils Protobuf sources were published without the associated DAML-LF sources, making them useless. This change adds the source JARs as runtime dependencies to ensure that when publishing a Protobuf source JAR, the release process will fail if the dependencies are not also published. CHANGELOG_BEGIN - [Ledger API] We now publish Protobuf sources in JARs for DAML-LF types to Maven Central, with the group "com.daml". The artifact names follow the format "<name>_proto_jar". CHANGELOG_END
2020-12-03 14:52:18 +03:00
- target: //ledger/participant-state/protobuf:ledger_configuration_proto_jar
type: jar-lib
Bazel: Factor out logic around Protobuf JARs. [KVL-714] (#8084) * kvutils: Use ScalaPB to generate a Scala JAR for daml_kvutils.proto. * Bazel: Delete the unused `da_java_binary` rule, and inline `_wrap_rule`. * Bazel: Factor out Java/Scala protobuf class generation into a helper. CHANGELOG_BEGIN CHANGELOG_END * daml-lf/archive: Use `proto_jars`. * Bazel: Remove the visibility modifier from `proto_jars`. It's too confusing. Just make everything public. * daml-lf/archive: Push protobuf source tarballs into `proto_jars`. * Bazel: Add comments to the various parts of `proto_jars`. * daml-assistant: Do unpleasant things with `location` in Bazel.
2020-11-27 11:34:53 +03:00
- target: //ledger/participant-state/protobuf:ledger_configuration_proto_java
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
type: jar-proto
- target: //ledger/participant-state-index:participant-state-index
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +03:00
type: jar-scala
kvutils/app: Add timing metrics for read/write/index services. (#5176) * participant-state{,-index}: Move Timed*Service classes from Sandbox. CHANGELOG_BEGIN - [Ledger Integration Kit] Metrics for the various read, write, and index services. CHANGELOG_END * kvutils/app: Add timing metrics for read/write/index services. * participant-state: Move metrics-related code to another Bazel package. * participant-state-metrics: Add to artifacts.yml. * participant-state-metrics: Move TimedIndexService back into Sandbox. Cuts down on dependencies like nobody's business.
2020-03-25 18:11:37 +03:00
- target: //ledger/participant-state-metrics:participant-state-metrics
type: jar-scala
Move Daml Profiler to EE version of sandbox/sandbox-classic (#9054) * Move Daml Profiler to EE version of sandbox/sandbox-classic This splits Sandbox targets into EE/CE targets and exposes the option in the EE version. The option still exists in the CE option for now until we have released EE artifacts to not break users that might know about it without an alternative. There is also a small test that makes sure that this actually works since classpaths are dumb and it didn’t work at first. changelog_begin changelog_end * Fix publish target changelog_begin changelog_end * Publish transitive dep changelog_begin changelog_end * I hate bash changelog_begin changelog_end
2021-03-09 21:35:14 +03:00
- target: //ledger/sandbox:sandbox-ce
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +03:00
type: jar-scala
Split sandbox code into separate packages (#6695) * Move public code into daml-integration-api CHANGELOG_BEGIN [DAML Integration Kit]: Removed sandbox specific code from the API intended to be used by ledger integrations. Use the maven coordinates ``com.daml:participant-integration-api:VERSION`` instead of ``com.daml:ledger-api-server`` or ``com.daml:sandbox``. CHANGELOG_END
2020-07-17 18:06:06 +03:00
- target: //ledger/sandbox-common:sandbox-common
type: jar-scala
Move Daml Profiler to EE version of sandbox/sandbox-classic (#9054) * Move Daml Profiler to EE version of sandbox/sandbox-classic This splits Sandbox targets into EE/CE targets and exposes the option in the EE version. The option still exists in the CE option for now until we have released EE artifacts to not break users that might know about it without an alternative. There is also a small test that makes sure that this actually works since classpaths are dumb and it didn’t work at first. changelog_begin changelog_end * Fix publish target changelog_begin changelog_end * Publish transitive dep changelog_begin changelog_end * I hate bash changelog_begin changelog_end
2021-03-09 21:35:14 +03:00
- target: //ledger/sandbox-common:sandbox-common-ce
type: jar-scala
- target: //ledger/sandbox-classic:sandbox-classic-ce
Split sandbox code into separate packages (#6695) * Move public code into daml-integration-api CHANGELOG_BEGIN [DAML Integration Kit]: Removed sandbox specific code from the API intended to be used by ledger integrations. Use the maven coordinates ``com.daml:participant-integration-api:VERSION`` instead of ``com.daml:ledger-api-server`` or ``com.daml:sandbox``. CHANGELOG_END
2020-07-17 18:06:06 +03:00
type: jar-scala
json-api: store contracts similar to Extractor's single-table (#3192) * new library ledger-service/db-backend * borrow contracts table schema from extractor * borrow contract insertion, removing some data to be unused * match contract schema with insert function * factor insertContract arguments * offset table declarations * CLI argument for query store * surrogate template IDs * compute surrogate template IDs on-the-fly * database init action * incoherent typeclasses, eh * newtype SurrogateTpId * offset fetch/update functions * bad sql * bulk insert contracts, function for selecting contracts * expose contract column name for query's usage * Initializing DB on startup if configured * dropping existing tables as part of initialization * fix some query syntax errors * createSchema flag * function for streaming transactions with jwt party selected * formatting * usage * collect acs contracts and the ledger offset at the end * lastOffset * fixing merge conflicts, updating the way 3rd party deps are specified * Moving ContractDao into http-json module so it can take domain AST as an input * cleanup * injecting new dependencies * split transaction batches into inserts and deletes * generate sql for deleting contracts * `fetch_sources = True` for java_deps * make the delete-constructed fragment more efficient; handle empty list here * pass logHandler for insertContracts * ContractDao returns ConnectionIO, it's up to the caller to wrap query into a transaction * fixing typo * minor cleanup, moving fromLedgerApi factory function into corresponding companion objects * don't need it any more * GetActiveContractsResponse => domain.Contract factory * make concatFragment private * add partition graph; move other contract-fetching experiments to ContractsFetch * experimenting with akka sources * introducing domain.Offset to work around API's empty/null offset cases * minor cleanup * decompose fetchActiveContractsFromOffset * missed via * ACS splitting graph * finish doc for ACS splitting graph * remove unneeded stages * WIP * lazily read a stream of ConnectionIO into a single ConnectionIO * cancel on IO error * figuring out how to put all the pieces together * graph WIP * Removing workflowId from the JSON API * simplify acsAndBoundary; describe other flow pieces * WIP * use Vector in InsertDeleteStep; add variant for ACS (no deletes) * `org.wartremover.warts.NonUnitStatements` enforced in `http-json` module * evaluate InsertDeleteStep to a ConnectionIO * database variant of LfValueCodec, using numbers for numbers * convert input to JSON, combine insert plans, connect rest of contractsToOffsetIo * remove strict contractsToOffset sink * moving dao methods into an object * putting pieces together * contractsFromOffset WIP * should be it * cleanup * cleanup * contractsIo that takes List[domain.TemplateId.RequiredPkg]) * contractsIo that takes List[domain.TemplateId.RequiredPkg]) * cleanup * put all pieces together, testing something does not work yet * diff is not required to return anything that is why Sink.lastOption that gives Option[domain.Offset] * factor out tuple split * use traverse syntax in contractsIo2 * factor explicit flow steps out of graph DSL; remove aggregate * locally model the Absolute/Begin distinction for offset bookmarking in DB * Adding test cases to run HTTP Service with Postgres backend the same set of test cases, run with and without DB backend * make better use of domain.Offset in OffsetBoundary * monomorphize InsertDeleteStep#append * Disabling a test that fails with DB backend * add release note * add release note about workflowId * a test case that checks the number or stored contracts * trying to figure out why Postgres test fails on Windows with NPE
2019-11-06 21:53:16 +03:00
- target: //ledger-service/db-backend:db-backend
type: jar-scala
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +03:00
- target: //ledger-service/http-json:http-json
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger-service/lf-value-json:lf-value-json
Publish the thin trigger library instead of the fat jar (#3739) This still contains the main class so you can use it like you would use the fat jar but publishing fat jars to maven central is apparently bad practise and some peple have asked for the library. This includes some slight tweaks to the scala_docs rule to make it capable of coping with the generated source file and a hack in the release script to avoid it complaining about the scenario proto library not being published to Maven even though it is included in the transitive deps.
2019-12-05 16:04:20 +03:00
type: jar-scala
allow secure connection from JSON API to ledger (#5555) * factor TlsConfiguration parser from extractor * move TlsConfigurationParser to new library * link extractor to ledger-service/cli-opts properly * use TlsConfigurationCli in http-json, pass SslContext to ledger-client * test TLS options as used in http-json - the TLS config code is shared with extractor, where it is more fully tested; we just do a sanity check here * doc TLS options for http-json CHANGELOG_BEGIN - [JSON API] New ``--pem``, ``--crt``, ``--cacrt``, and ``--tls`` options for securing the connection between JSON API server and ledger. See `issue #2540 <https://github.com/digital-asset/daml/issues/2540>`__. CHANGELOG_END * TLS off in daml-script JSON API test
2020-04-16 20:12:30 +03:00
- target: //ledger-service/cli-opts:cli-opts
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //ledger-service/jwt:jwt
type: jar-scala
- target: //ledger-service/utils:utils
Upload codegen fat-jars to maven central (#3476)
2019-11-14 20:40:54 +03:00
type: jar-scala
Spin off TokenHolder into a new library (#3741) * Spin off TokenHolder into a new library Avoids having weird dependencies between different packages, makes TokenHolder available on Maven * Fix auth-utils path
2019-12-05 15:31:14 +03:00
- target: //libs-scala/auth-utils:auth-utils
type: jar-scala
reorder some of the libs-scala artifacts (#7433) - suggested by @SamirTalwar-DA in #7347; thanks CHANGELOG_BEGIN CHANGELOG_END
2020-09-17 20:12:40 +03:00
- target: //libs-scala/build-info:build-info
type: jar-scala
- target: //libs-scala/concurrent:concurrent
type: jar-scala
contextualized-logging: Move to its own Bazel package. (#4138) I want to use this in _ledger/ledger-on-sql_, which doesn't depend directly on Sandbox. CHANGELOG_BEGIN CHANGELOG_END
2020-01-21 16:25:06 +03:00
- target: //libs-scala/contextualized-logging:contextualized-logging
type: jar-scala
Add //libs-scala/doobie-slf4j and replace usages of jdkLogHandler (#8731) The jdkLogHandler provided by Doobie exists purely as an example and the library itself does not recommend using it in production. Note that this slightly changes the runtime behavior, logging successful queries at debug level rather then info. The message itself is preserved from the original MIT-licensed example. This uses Slf4j as most of our components, instead of java.util.logging. changelog_begin [HTTP JSON API] The server now logs successful queries at debug level instead of info [Trigger Service] The server now logs successful queries at debug level instead of info changelog_end
2021-02-03 13:45:05 +03:00
- target: //libs-scala/doobie-slf4j:doobie-slf4j
type: jar-scala
Extractor with authentication (#3514) * Make Extractor work against Ledger API servers protected by authentication * Update changelog * Address https://github.com/digital-asset/daml/pull/3514#pullrequestreview-318811500 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753205 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753629 - https://github.com/digital-asset/daml/pull/3514#discussion_r347754462 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347755484 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347752424 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347756328 * Fix docs * Fix artifacts.yaml
2019-11-19 19:12:25 +03:00
- target: //libs-scala/grpc-utils:grpc-utils
type: jar-scala
libs-scala/ports: Wrap socket ports in a type, `Port`. (#4784) * libs-scala/ports: Wrap socket ports in a type, `Port`. * sandbox: Use `Port` for the API server port, and propagate. CHANGELOG_BEGIN CHANGELOG_END * extractor: Use `Port` for the server port. * ports: Make Port a compile-time class only. * ports: Allow port 0; it can be specified by a user. * ports: Publish to Maven Central.
2020-03-03 11:59:15 +03:00
- target: //libs-scala/ports:ports
type: jar-scala
libs-scala/resources: Move `Resource` and friends to their own package. (#4066) * libs-scala/resources: Move `Resource` and friends to their own package. CHANGELOG_BEGIN - [Ledger API Server] Publish the resource management code as a library under ``com.digitalasset:resources``. CHANGELOG_END * libs-scala/resources: Add to the artifacts list. * libs-scala/resources: Factor out the test helpers into test/lib. * libs-scala/resources-akka: Make the Akka resources an optional dep.
2020-01-16 17:13:18 +03:00
- target: //libs-scala/resources:resources
type: jar-scala
- target: //libs-scala/resources-akka:resources-akka
type: jar-scala
Add a library that defines Resource factory methods for gRPC servers and channels (#8604) * Add a library that defines Resource factory methods for gRPC servers and channels This is the first of four PRs in which https://github.com/digital-asset/daml/commit/6ea70c4b45d55cbf62caa3cc03dd70310ca79b87 has been broken up to facilitate review. The endgame is to have the non-repudiation prototype merged. These factory methods have been used to make resource management easier, specifically as part of testing. changelog_begin changelog_end * Let warning log output in tests Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org> * Address https://github.com/digital-asset/daml/pull/8604#discussion_r562634032 * Address https://github.com/digital-asset/daml/pull/8604#discussion_r562634865 * Address https://github.com/digital-asset/daml/pull/8604#discussion_r562635148 * Address https://github.com/digital-asset/daml/pull/8604#discussion_r562635684 * Add resources-grpc to release/artifacts.yaml Co-authored-by: Moritz Kiefer <moritz.kiefer@purelyfunctional.org>
2021-01-25 12:32:36 +03:00
- target: //libs-scala/resources-grpc:resources-grpc
type: jar-scala
reorder some of the libs-scala artifacts (#7433) - suggested by @SamirTalwar-DA in #7347; thanks CHANGELOG_BEGIN CHANGELOG_END
2020-09-17 20:12:40 +03:00
- target: //libs-scala/scala-utils:scala-utils
type: jar-scala
equalz Scalatest matcher in new daml-lf/scalatest-tools library (#1200) * equalz Scalatest matcher in new daml-lf/scalatest-tools library * equalz typing tests * a 'should' replacing design * a 'MatcherFactory1' design - this fails because the TC parameter should be a type member to avoid scala/bug#5075 but it is not * MatcherFactory1 with chained Lub+Equal typeclass - requires partial-unification at point of use, which is not great * LubEqual's extra tparam is probably unneeded * better LtEqual * demonstrate that HK LubEqual's resolve with DMT should + MatcherFactory * remove unneeded 3rd param from LubEqual, again * update dependency specs and license headers * allow use with should, shouldNot in some cases, preserving the shouldx/shouldNotx alternatives * move Equalz to libs-scala/scalatest-utils * rename bzl targets and place in com.daml.scalatest package * add scalatest-utils to release * move *SpecCheckLaws, Unnatural to scalatest-utils * missed scalacheck dep in scalatest-utils * downstreams of *SpecCheckLaws now get them from scalatest-utils * test equal-types case as well * update LF documentation CHANGELOG_BEGIN CHANGELOG_END * whitespace error
2020-05-28 00:25:43 +03:00
- target: //libs-scala/scalatest-utils:scalatest-utils
type: jar-scala
Extractor with authentication (#3514) * Make Extractor work against Ledger API servers protected by authentication * Update changelog * Address https://github.com/digital-asset/daml/pull/3514#pullrequestreview-318811500 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753205 - https://github.com/digital-asset/daml/pull/3514#discussion_r347753629 - https://github.com/digital-asset/daml/pull/3514#discussion_r347754462 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347755484 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347752424 * Address https://github.com/digital-asset/daml/pull/3514#discussion_r347756328 * Fix docs * Fix artifacts.yaml
2019-11-19 19:12:25 +03:00
- target: //libs-scala/timer-utils:timer-utils
type: jar-scala
release: Sort artifacts.yaml. (#4502) I verified that there are no semantic changes, only cosmetic ones, by running the following before and after, and checking the diff. ``` < release/artifacts.yaml ruby -rjson -ryaml -e 'puts JSON::generate YAML::load $stdin' | jq '. | sort_by(.target)' > ~/Desktop/artifacts.{old,new}.json ``` CHANGELOG_BEGIN CHANGELOG_END
2020-02-13 16:52:48 +03:00
- target: //triggers/runner:trigger-runner-lib
type: jar-scala
Reference in New Issue Copy Permalink