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
d7d45d1860
daml/release/artifacts.yaml

227 lines
7.4 KiB
YAML
Raw Normal View History

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
# Copyright (c) 2020 The DAML Authors. All rights reserved.
# 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
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/archive:daml_lf_1.6_archive_java_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
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
javadoc-jar: daml_lf_1.6_archive_java_proto_javadoc.jar
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_tarball
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: targz
location:
groupId: com.digitalasset
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
artifactId: daml-lf-1.6-archive-proto
# This is a tarball instead of a jar.
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
mavenUpload: false
daml-lf proto: archive proto for daml-lf 1.6 (#3142) * daml-lf proto: archive proto for daml-lf 1.6 * try to fix archive ProtoTest for windows * more windows fix for archive ProtoTest
2019-10-15 21:35:20 +03:00
- target: //daml-lf/archive:daml_lf_1.6_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-1.6-archive-proto
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is a zip archive instead of a jar.
mavenUpload: false
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/archive:daml_lf_1.7_archive_java_proto
type: jar-lib
javadoc-jar: daml_lf_1.7_archive_java_proto_javadoc.jar
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_tarball
daml-lf proto: archive proto for daml-lf 1.6 (#3142) * daml-lf proto: archive proto for daml-lf 1.6 * try to fix archive ProtoTest for windows * more windows fix for archive ProtoTest
2019-10-15 21:35:20 +03:00
type: targz
location:
groupId: com.digitalasset
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
artifactId: daml-lf-1.7-archive-proto
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is a tarball instead of a jar.
mavenUpload: false
daml-lf: clone dev protobuf for LF 1.7 (#3371)
2019-11-07 15:32:38 +03:00
- target: //daml-lf/archive:daml_lf_1.7_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-1.7-archive-proto
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is a zip archive instead of a jar.
mavenUpload: false
Freeze DAML-LF 1.8 proto (#4788) * Freeze DAML-LF 1.8 proto This is a copy of the 1.dev proto with the following changes that overall remove all references to 1.dev: * Change the versions and the reference to the spec. * Remove `dev` from version history at the top. * Remove `GENMAP` and corresponding primitives. * Remove general equality `EQUAL` and the comments that the type-specific equality primitives are only available in < 1.dev * Remove experimental text primitives. changelog_begin changelog_end * windows is very bad * bump windows hashes
2020-03-03 16:21:00 +03:00
- target: //daml-lf/archive:daml_lf_1.8_archive_java_proto
type: jar-lib
javadoc-jar: daml_lf_1.8_archive_java_proto_javadoc.jar
- target: //daml-lf/archive:daml_lf_1.8_archive_proto_tarball
type: targz
location:
groupId: com.digitalasset
artifactId: daml-lf-1.8-archive-proto
# This is a tarball instead of a jar.
mavenUpload: false
- target: //daml-lf/archive:daml_lf_1.8_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-1.8-archive-proto
# This is a zip archive instead of a jar.
mavenUpload: false
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/archive:daml_lf_dev_archive_java_proto
type: jar-lib
javadoc-jar: daml_lf_dev_archive_java_proto_javadoc.jar
- target: //daml-lf/archive:daml_lf_dev_archive_proto_tarball
daml-lf: clone dev protobuf for LF 1.7 (#3371)
2019-11-07 15:32:38 +03:00
type: targz
location:
groupId: com.digitalasset
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
artifactId: daml-lf-dev-archive-proto
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is a tarball instead of a jar.
mavenUpload: false
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/archive:daml_lf_dev_archive_proto_zip
type: zip
location:
groupId: com.digitalasset
artifactId: daml-lf-dev-archive-proto
# This is a zip archive instead of a jar.
mavenUpload: false
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
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/repl:repl
type: jar
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is an internal tool not something we want to make public
mavenUpload: false
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:blindinginfo_java_proto
type: jar-proto
- target: //daml-lf/transaction:transaction
type: jar-scala
- target: //daml-lf/transaction:transaction_java_proto
type: jar-proto
- target: //daml-lf/transaction:value_java_proto
type: jar-proto
- target: //daml-lf/transaction-scalacheck:transaction-scalacheck
type: jar-scala
- target: //daml-lf/validation:validation
type: jar-scala
- target: //extractor:extractor-binary
type: jar-deploy
# This is a fat jar.
mavenUpload: false
- target: //language-support/codegen-common:codegen-common
type: jar-scala
- target: //language-support/codegen-main:shaded_binary
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: //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
type: jar-scala
- 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
- target: //language-support/scala/codegen:codegen-main
type: jar
# This is a fat jar.
mavenUpload: false
- target: //ledger-api/grpc-definitions:ledger-api-protos-tarball
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: targz
location:
groupId: com.digitalasset
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
artifactId: ledger-api-protos
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/grpc-definitions:ledger-api-scalapb
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
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
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
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
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
- target: //ledger/participant-state/kvutils:daml_kvutils_java_proto
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
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/participant-state/protobuf:ledger_configuration_java_proto
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
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/sandbox:ledger-api-server
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +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/sandbox:sandbox
Releasing //ledger-service/http-json module and its dependencies (#2543)
2019-08-14 20:19:31 +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/sandbox:sandbox-tarball
type: targz
location:
groupId: com.digitalasset
artifactId: sandbox
# This is a tarball of the fat jar.
mavenUpload: false
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
Releasing http-json-binary (#2751) com/digitalasset/ledger-service/http-json-deploy/100.13.21
2019-09-04 22:47:24 +03:00
- target: //ledger-service/http-json:http-json-binary
type: jar-deploy
Flip the default on mavenUpload in artifacts.yaml (#4396) changelog_begin changelog_end
2020-02-05 12:32:02 +03:00
# This is a fat jar.
mavenUpload: false
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
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
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
Moves CommandCompletionIT to Ledger API Test Tool (#3901) * Moves CommandCompletionIT to Ledger API Test Tool Closes #2841 Also refactors test observers into a single API and unifies the existing implementations of the DirectExecutionContext * Allow explicit offsets to get checkpoints * Raise checkpoint test timeout * Consolidate checkpoint tests in a single test case * Fix compilation issues * Exclude command submission/completion tests for rev-v2 * Drop test not relevant for Ledger API implementations * Fix compilation errors
2019-12-20 17:55:23 +03:00
- target: //libs-scala/direct-execution-context:direct-execution-context
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
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: //navigator/backend:navigator-binary
type: jar-deploy
# This is a fat jar.
mavenUpload: false
- target: //triggers/runner:trigger-runner-lib
type: jar-scala
Spin-off BuildInfo into its own (micro-)library (#5004) * Spin-off BuildInfo into its own (micro-)library CHANGELOG_BEGIN CHANGELOG_END * Fix dependencies * Remove unused dependency
2020-03-16 11:04:00 +03:00
- target: //libs-scala/build-info:build-info
type: jar-scala
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
Reference in New Issue Copy Permalink