release 2.0.0-snapshot.20220126.9029.0.42cf70b1 (#12603)
This PR has been created by a script, which is not very smart
and does not have all the context. Please do double-check that
the version prefix is correct before merging.
@stefanobaghino-da is in charge of this release.
Commit log:
```
42cf70b18ec626a4294b25a2d2932f6b674c28cb ci: try to fix release process (#12600)
0579ebdd770ab0f6a8cbbd45a09726dc79e9daa7 Mark the `withExpectedLedgerId` method in `DamlLedgerClient.Builder` as deprecated (#12537)
deb7f3a628b9250630196b958336f00635e007f9 Move some trigger compat tests to sandbox-on-x (#12598)
5cdf9b95fb5ddafc08343e86e0bc5a57a00273f7 Remove some unecessary `implictly` with `Factory` (#12559)
9c3f1ce93a4ee15735d4c073d7e11233074dfae9 Drop dummy token from JSON API check (#12593)
3366c6f39b885ecebf7e61d117193b328c420887 compatibility: Exclude another command deduplication test. (#12592)
54339ada82342e04e7e4ebfd985c546b8c6ceb6c Safeguard Oracle CI tests with lockIdSeed [DPP-802] (#12573)
5cccec2fe31fcff83c1a9b74fd9ea1bfe3a096ae release: use-devenv (#12583)
90aacea36c6758fbf22ecd5b78fb2dd34a16a840 split-release (#12577)
cc19df44a832614caa38d6a69d298731a114bbf2 Persist transaction metering info [DPP-814,DPP-821] (#12274)
cb77c84cc76ee4abe00fc0c8e250225517cd6a49 damlc: Don't rely on worker for zero argument polymorphic type constructors (#12581)
ed33c0d5db7df914329791abb6e50830fc3f2af8 split: flat(ter) files in Artifactory (#12575)
e355832bc191b98c5ca42189d80703012970be8c split: do not push exe (#12574)
0afc4a5553f8c746d414f70569420036f89050c5 split: do not tag (#12569)
ebf79080079d48a580d8137b959649584b5f807c LF: check contracts are consumed when found them in the cache (#12527)
ce06eb00fbb0dfc21de92345eba4a53a94c6ae8d Add serializability check for interface payloads in Haskell (#12560)
aced78f0b4d383a693188d22f817b333728c1106 Drop dadew uninstall (#12566)
ac3ca1d20c5216dcc2489998d06fab73cb57f46e ledger-api-test-tool: Enable command deduplication tests by default [KVL-1261] (#12541)
5f58698ba6c60edc0843ee6fbb6dc440366ef37d [JSON-API] Add list-specific-users-rights, grant & revoke user rights endpoints (#12352)
42aadec073a7420fce4cf65c56a210b53d217ee1 Cleanup Haskell serializability check (#12565)
5d93eb93e8ca0ee42a598c201628c2b857b9300b Engine stacktraces are disabled by default (#12562)
42d86acd06857733694cd0ac405d7559701e48a1 [User management] Disabling user management in auth when user management feature is disabled [DPP-827] (#12503)
13153de88f456536594a53b3912cb32febbf7b89 update NOTICES file (#12564)
5bfe4ed58941c8982268112628e1e19940d8f3ba Wait for server process in client_server_test (#12551)
f1cd4b1c7c4c9fa0d96cf23043538c4d2d31a104 Remove dependencies on compatibility libraries (#12548)
dcd721da9939f2502b401c569f10b92179f2ede3 Drop scenarios (#12484)
170d839ed0183efd3e979fcfa3f52038190f00e2 Fix es (#12554)
8fa54c67ce32b1ef3a54a7ca83af653d9bb58254 Experimental daml assistant support for metering report [DPP-816] (#12485)
9802028380965d575be8edd7055f29a67d61712c Cut a new split release (#12547)
aec3390904ccc341648f4a9dc1761efb723d41b2 Replace silencer plugin with built-in warning configuration (#12543)
93cfe043f8523874e1603a56b6f3a2985f1bc103 Remove from the Java bindings constructors that were deprecated since 0.x (#12536)
8d65aa3b4d1e4209e498c920bc26f86ea5c691a2 Remove Sandbox classic stores and related unit tests (#12532)
24b2325d19125c5cadc7096d16a35229b51ae342 Bump node-fetch to address dependabot alerts (#12553)
fdb034ca948972099ec96ebab8d92f27c925a26f split-release: Canton dependencies to public GCS (#12552)
3f8ec07bdfb6dd40655722d4c2feab07704edf96 Upgrade to the latest Canton snapshot (#12544)
8692d80b33e8e3a6557aea49f5db0d9559fb8116 Fix trigger compat test for canton sandbox (#12549)
3ea8aded13685972427a23b7447fca927af68da8 LF: Test evaluation order of exercise and exercise_by_key (#12519)
36f8d67c599ec6e5fa2ac485d9ae7b647670d7e2 Upgrade `css-loader` to 5.2.7 (#12550)
a150737d170fe2589a870e1f99e70a830419f3a4 Upgrade msys2 (#12545)
01447fd48969c8a838e85cd712a7c4ba649847e4 docs: typos and minor clarification for authz docs (#12534)
fbf244e2f8df3938e27d761314d213eb0c95bd45 alert on invalid users in create-daml-app (#12518)
f2b4abe187e982519ec8cf2ee2a8a3992c70220f update NOTICES file (#12542)
bd0ae0239b69ee0078ec5a18447092c159ceda86 Startup initialization header for runners [DPP-860] (#12525)
15c0ad7efa1724b06cd8c8abe249f756576a4b76 Migration DB unit testing for PostgreSQL v111 to v116 [DPP-756] (#12517)
7218e6f95dfd05670158e2afa3fcf6795f363f2e ledger-api-test-tool: Remove retired tests. (#12535)
cbb4986e8905cb6637d34048c41b988c1e115585 Add Empty GRPC Metering Report Service [DPP-856] (#12515)
4d26f0899eb887cfd4321052773b277d04fce5a0 ledger-api-test-tool: Enable ParticipantPruningIT for everyone. [KVL-1261] (#12529)
3044958cdfa9efe06f2ccd898339b81b0fb27f1f ledger-api-test-tool: Remove deprecated options. (#12533)
5ab9eae033afbfb2e2fa7321484f4d15ae4f8146 Make mutable-contract-state-cache the default and only option (#12528)
89d95e6d6c403a6e9555842ea2b2d76719090fa3 user management: allow ':' in user ids (#12531)
f5d7821ace6cad3da43838858955ea919202c28f compatibility: Disable MultiParticipantIT for old versions. (#12526)
2deeabf3fac6ec6d75f9d779f4acde1c0dacc56b [User management] Add feature flag to enable user management [DPP-827] (#12420)
b8431175012cf8dc4ea4e131aa10e0ff3f648035 Drop feature flag for v0 cid support (#12522)
73277f4210f39d1cb3e32b84ce79b80c72177cbd Upgrade to oracle 19.14 image for ci (#12523)
cdde8df9fd32bd575689b83b4ada5ddf8a1d7891 ledger-api-test-tool: Add assertions and a test case for successful completions when converting deduplication durations to offsets [KVL-1220] (#12462)
2267d1a15d3927f29b4829f63ac219076d4376e4 sandbox-classic uses Sandbox-on-X internals [DPP-860] (#12466)
20cda0181a83979900e8c6603106dad6d24c46c7 specify that deduplication offsets are exclusive (#12488)
e9e1b06da558101b06ffc4b1c6d593c262a20f23 ledger-api-test-tool: Enable `MultiPartySubmissionIT` for everyone. [KVL-1261] (#12500)
a5f56e0671feb14235d72e6226dd61137488877e Use canton sandbox in script+trigger compat tests (#12514)
9c03e7908bbd85ab1f8686cc581d49cc93beea92 Build create-daml-app with -Werror (#12513)
688f1e1e0b4818c1f918199dfe11ab38de4a1f61 Drop v0 contract ids (#12464)
c35d34db3da262ebe20e203973883eea56db8393 Remove ResetService from the grpc documentation (#12512)
eb618935ffac10a82f6ea0b588dcf106846bdf0b resources: Remove ResettableResourceOwner. (#12499)
7880d5416deb456dfe62bc35737afdb8e5764d88 Add --port-file and --dar flags in daml sandbox (#12505)
3c8a6468fb16719f5a70195a9e70eac6f4605dc0 Tell users to use --install-assistant=yes (#12507)
36536fabfa3f429bd1605693425fc362604d839f LF: Test evaluation order of lookup_by_key (#12494)
ad7ce54075366f2b1509adce048fdf932e57e26a participant-integration-api: Factor out feature flags into a class. (#12496)
4d698c111a8b5cf5f0690a42b1aeb1b535fee0c7 Update windows testing instructions (#12504)
0f8e40c92d9853d10fd936c6a7934c7b0cf5cd25 user management: add reference docs (#12398)
96b8651863cebbe961d60d6b3bab8685a2ce2a2e Drop orphaned vim syntax files (#12502)
a6444065394eb9d9c9e3e76dcea7eb1aa4847b2a Avoid stale DAML_SDK_VERSION_LATEST in assistant (#12493)
7a1b37c1a142835f146467b8fce3f0b88993e8db [User management] Nullable primary_party and for_party (#12419)
cd30f017795e35c445441359fc16c796091e0821 update NOTICES file (#12498)
b11f11bde0a397cdaae5c43adf2035af36f35830 Drop support for no seeding in sandbox-classic (#12495)
5d2be1e1fd3b7f1c657b59aabea11f9ade661fbe ledger-api-test-tool-on-canton: Use `join` to clean up exclusions. (#12497)
072d57a831a03188162b53b14641e62e8497173f DPP-553 Consistently use anorm string interpolation (#12266)
f03fa6a5f178fb381f64dae5927cae9c4e0a2a17 ledger-api-test-tool: Govern ContractIdIT test runs through a feature. (#12454)
dd4fc1f755a3e60a1a80f8fb7236501b8dd90580 split release (#12492)
de2a8c0c049082f48b9a5b8e54a5943acbefbeff ci: use service account for Windows nodes (#12489)
644efd155d6d64f1426c54e99d7995292875e751 Lower log level to warn (#12490)
ebd3827c4af11024a3a397bf07d7b5c10ffa7c51 Make UserId properly opaque by defining it as a variant (#12476)
3159d60444a5b42d46d5e8ccdbd0f24eef60f8e7 LF: more tests for evaluation order of fetch (#12471)
96f454acdd925d89f00d259ab036b0ae134d6574 update compat versions for 1.18.1 (#12430)
82639a136025c8c4afe3ba6474e3c25cdf788bce Fix get-daml.sh installation script (#12487)
e222c355120eb38dfeeea899034d70c7eea824be Enhance conformance test: ACS coverage [DPP-672] (#11334)
244389152f9a920cb0272cef5fae0f3379cbb7ee Remove /user/delete GET endpoint (#12486)
681f8fca6b64249ab15202484d3c6e1c5df62736 Add missing serializability checks for interfaces (#12483)
7c597281464fcdfd9d361487626dedbc51271819 Remove reset service support from the storage backend [DPP-804] (#12477)
f7e2faf5aae99fab8bb3ca1ea28e1482027d9fb8 [User management] Addressing outstanding code review comments from https://github.com/digital-asset/daml/pull/12344# (#12479)
350fe5c1c64b26c15ab14a354faa0a75c60e1182 Update RELEASE.md (#12481)
82534f9155c777c7f533d71e5d3faf2d091b61a5 Remove the reset service from the ledger api and the documentation [DPP-804] (#12472)
4885e610e6bf1328d58462c451ba3eadaedffdb8 rotate release duty after 2.0.0-snapshot.20220118.8919.0.d0813e61 (#12468)
9518f15408ced6bd2fe503dfcfe214c7b38386fe Fix sandbox on x compat test switch (#12478)
66494a26aa7b8a6233af23185c5eafcc2e9c7c73 [User management] created_at and granted_at in Oracle (#12417)
6fbaac467fe2a194818134f44bdd2cb83547bcdb Remove user-management error cases from scenario-service proto. (#12460)
1f1e8bfe2e3dd5d12fc41c8866349560eb58131f [DPP-829] Make ledger-id field optional in requests (#12243)
74e9efcc854b04ee5b97d570d4c9bcc6960ad32b release 2.0.0-snapshot.20220118.8919.0.d0813e61 (#12467)
d0cbccb4d3a8602626f9db6b35ecc2a8b8fe1f77 Explicitly name coalesced columns (#12377)
954bc5e0d414d46194a1868fcfec719d29424125 Remove the reset service from sandbox-classic and sandbox [DPP-804] (#12448)
e40c221b8edfd4b5855a26b1d9ca55d360b94487 Fix compatibility tests. (#12465)
```
Changelog:
```
[Java bindings] Deprecate `DamlLedgerClient.Builder.withExpectedLedgerId`
Transaction Metering now persisted to database
- [Ledger API Test Tool] More command deduplication tests have been
enabled by default. This should not affect testing a fully functioning
ledger. If any tests fail, they can be temporarily excluded.
- [HTTP-JSON] Added endpoint /user/rights that if called with POST will return user rights of the user specified via the payload
- [HTTP-JSON] Added endpoints user/rights/grant & user/rights/revoke which allow granting & revoking user rights for a specific user
Add experimental Daml assistant support for ledger metering
[Java bindings] `DamlLedgerClient.forLedgerIdAndHost` and `DamlLedgerClient.forHostWithLedgerIdDiscovery` static methods
and the constructor taking a `ManagedChannel`, which were all deprecated since 0.13.38, have been removed.
- [Ledger API Test Tool] The retired test suites, ``LotsOfPartiesIT``
and ``TransactionScaleIT``, have been removed in favor of more
targeted benchmarking tests. If you are actively including these tests
in your test run, you will need to remove them. These tests are
disabled by default so it is likely that no change will be needed.
- [Ledger API Test Tool] The ``ParticipantPruningIT`` test case has
been enabled by default. You may need to disable specific test cases
accordingly.
Sandbox: Participant server now supports '--feature-user-management' flag to turn on or off user management feature.
- [Ledger API Test Tool] The ``MultiPartySubmissionIT`` test case has
been enabled by default. You will most likely not need to change
anything.
- [Ledger API Test Tool] The "ContractIdIT" test is now run by default,
using ledger feature flags to determine which test cases are run. You
will need to configure the ``StandaloneApiService`` accordingly.
- [HTTP-JSON] Removed the /user/delete GET endpoint. Please use the /user/delete POST endpoint with the own user ID if you need to delete the user associated with the current token
Remove reset service from the ledger api protocol and the documentation
The field "ledger_id" in all request to Participant API is now optional (was required).
Reset service has been removed from the sandbox-classic, sandbox and daml-on-sql
```
CHANGELOG_BEGIN
CHANGELOG_END
2022-01-26 19:37:25 +03:00
|
|
|
42cf70b18ec626a4294b25a2d2932f6b674c28cb 2.0.0-snapshot.20220126.9029.0.42cf70b1
|
2022-01-25 22:11:41 +03:00
|
|
|
ed33c0d5db7df914329791abb6e50830fc3f2af8 2.0.0-snapshot.20220125.9008.0.ed33c0d5 SPLIT_RELEASE
|
2022-01-17 11:51:13 +03:00
|
|
|
1724373fd395bb1fc604ea8628dce89110d1467f 1.18.1
|
2021-12-08 22:26:33 +03:00
|
|
|
2c945fcb3a2ca0972fbf8f222420b286f20b29e7 1.18.0
|
2021-12-02 13:22:48 +03:00
|
|
|
b33b94b85c23235a9d62fb7a9967f1f91247ed76 1.17.2-snapshot.20211124.7857.0.b33b94b8
|
2021-10-11 10:04:21 +03:00
|
|
|
e05be36512ade4d9cb6921614c23dadbde1747a3 1.17.1
|
2021-09-29 13:44:34 +03:00
|
|
|
49a75801fbafa1ffab3247ecfbb06a82925e8a0b 1.17.0
|
2021-08-11 13:13:06 +03:00
|
|
|
48050ad7836b9825c9dc7bd96fbc980b8eb9b6e5 1.16.0
|
2021-07-14 18:23:13 +03:00
|
|
|
aca22721f709d879a49fa958a1eb0b532fcbde54 1.15.0
|
2021-07-09 13:09:31 +03:00
|
|
|
aa2978400dd88a6011db18a62fb71c23ebd9d20b 1.14.2
|
2021-06-17 11:11:09 +03:00
|
|
|
d1b54ff0a0213d0f88a30078dacae06744529773 1.14.0
|
2021-05-17 12:42:07 +03:00
|
|
|
5f5323806b9ee704dc7f5bed5c458ee9d0c431f7 1.13.1
|
2021-05-12 11:32:09 +03:00
|
|
|
9ae787d005a5ea5c3c65aef9f56a56082ea4c167 1.13.0
|
2021-04-14 11:40:41 +03:00
|
|
|
631db446f0e5f24845b9837ffcf8ea6061f91f4f 1.12.0
|
2021-12-07 15:28:15 +03:00
|
|
|
c679b4ab238f183fc54d7118e5a633097cb4813b 1.11.3
|
2021-06-23 19:26:47 +03:00
|
|
|
a08f6ea24245461e912f2be5676009dcbea05634 1.11.2
|
2021-03-17 12:52:56 +03:00
|
|
|
7cd6380e156810ec7a19abbb3b967f45acab00b9 1.11.1
|
2021-03-10 12:14:25 +03:00
|
|
|
d3d5042ac04f4c0f755df7e87bc191716fdecc4c 1.11.0
|
2021-03-03 21:31:53 +03:00
|
|
|
80d080ef9f1c63de6f94d22592f89d623bfb1fa6 1.10.2
|
2021-02-17 15:17:12 +03:00
|
|
|
19bf4031f551334ff70a77bbf469b8af8e061bf2 1.10.0
|
2021-01-20 18:42:38 +03:00
|
|
|
5b3663a500e6840109e0e3e21cd6dea3c546573d 1.9.0
|
2021-03-03 20:44:59 +03:00
|
|
|
d443707c1893b58206f2f2ba62a18cd25e1ff53c 1.8.0-snapshot.20210303.5843.0.d443707c
|
2021-01-18 17:08:19 +03:00
|
|
|
59f5d40754bebf76f0530d94eb4c723cba21a21b 1.8.1
|
2020-12-16 11:46:55 +03:00
|
|
|
38455e8ca91ca3c351a6d15bd9ec25070386fc6c 1.8.0
|
2020-11-11 12:26:41 +03:00
|
|
|
e75d42ddc3150c0e054c35cc8c5afcf523ed5702 1.7.0
|
2020-12-21 17:17:34 +03:00
|
|
|
547abc97d96ad9ab4ed6e5fb6acf4c05ae85b639 1.6.1
|
2020-10-15 11:47:32 +03:00
|
|
|
d21cb496b7373dcf5c7afcc373b7898cbe54019e 1.6.0
|
2020-09-16 11:51:45 +03:00
|
|
|
eb68e680f649bc7c2b6b2c3b8a4c7a664f52ecec 1.5.0
|
2020-08-12 14:12:17 +03:00
|
|
|
224ab3621c8c3745aa5af78f655b4676794d7a5f 1.4.0
|
2020-07-16 13:07:34 +03:00
|
|
|
8e10c7a7338d72b907ae72f77c03b06cbe8426af 1.3.0
|
2020-07-06 16:06:48 +03:00
|
|
|
11b5c36282407284122326c4d80cb7a6015ed825 1.3.0-snapshot.20200610.4413.0.11b5c362
|
2020-06-10 13:36:31 +03:00
|
|
|
1c18058f019229cd0af64669af0de31d0cec916d 1.2.0
|
trigger all releases from master (#6016)
trigger all releases from master
The 1.1.0 release went wrong and we had to trash it and release 1.1.1
instead. This is an attempt at identifying and correcting the root
cause behind that incident.
To understand the situation, we need to know how releases worked before
1.0. We had a one-line file called `LATEST` that specifies the git SHA and
version tag for the latest release. A change to that file triggered a
release with the specified release tag, built from the source tree of
the specified commit. The `LATEST` file looked something like:
```
f050da78c9c8727b889bdac286156f19e2f938c4 1.0.0-snapshot.20200411.3905.0.f050da78
```
To mark a release as stable, we would change it to look like this:
```
f050da78c9c8727b889bdac286156f19e2f938c4 1.0.0
```
i.e. simply drop the `-snapshot...` suffix. Even though the commit (and
thus the entire source tree we build from) is the same, we would need to
rebuild almost all of our release artifacts, as they embed the version
tag in various places and ways. That worked well as long as we could
assume we were doing trunk-based development, i.e. all releases would
always come from the same (`master`) branch.
When we released 1.0, and started work on 1.1, we had a few bug reports
for 1.0 that we decided should be resolved in a point release. We
decided that the best way to handle that would be to have a branch
starting on the release commit for 1.0, and then backport patches from
`master` to that branch. We adapted our build process to also watch the
`release/1.0.x` branch and, in particular, trigger a new release build if
the `LATEST` file in that branch changed. That worked well.
The plan going forward was to keep doing regular snapshot releases from
the `master` branch, and create support, point releases ("patch" releases
in semver) from dedicated branches.
On April 30, we made a snapshot release as an RC for 1.1.0, by changing
the `LATEST` file in the `master` branch. That release was built on commit
681c862d. On May 6, we decided to take a new snapshot as the RC for
1.1.0; we changed `LATEST` in `master` to designate 7e448d81 as the new
latest release.
On May 11, we noticed an issue that broke our builds. Without going into
details, an external artifact we depend on had changed in incompatible
ways. After fixing that on `master`, we reasoned that this would also
break the build of the final 1.1.0 release if we just tried to build
7e448d81 again. But as the target release date was May 13, we did not
want to take a new snapshot after that fix, as that would have included
one more week of work in the release, and given us no time to test it.
So we did what we did for the 1.0 branch, as it had worked well: we
created a branch that forked from `master` at commit 7e448d81 and called
it `release/1.1.x`, then cherry-picked the one fix to our build process to
work around the broken download. When the time came to make the final
1.1.0 build on May 13, we naturally picked the `LATEST` file from the
`release/1.1.x` branch and dropped the `-snapshot...` suffix. Importantly,
we did not need to update the target commit to include the "broken
download" fix as, in the meantime, the internet had fixed itself, and we
thus reasoned we should go for the exact code of the RC rather than
include an unnecessary, albeit seemingly harmless, change.
Everything went well with the release process. Tests went well too. Then
we got a report that an application that worked against the latest RC
broke with the final 1.1.0. The issue was that we had built the wrong
commit: by branching off at the point of the _target_ commit for the
latest snapshot, we did not have the change to the `LATEST` file that
designated that commit as the target. So the `LATEST` file in
`release/1.1.x` was still pointing to 681c862d.
I believe the root cause for this issue is the fact that we have
scattered our release process over multiple branches, meaning there is
no linear history of what was released and we are relying on people
being able to mentally manage multiple timelines. Therefore, I propose
to fix our release process so this should not happen again by
linearizing the release process, i.e. getting back to a situation where
all releases are made from a single branch, `master`.
Because we do want to be able to release _for_ multiple release branches
(to provide backports and bugfixes), we still need some way to
accommodate that. Having a single `LATEST` file in the same format as
before would not really work well: keeping track of interleaved release
streams on a single file would not really be easier than keeping track
of multiple branches.
My proposed solution is to instead have a multiline LATEST file, so that
all the release branch "tips" can be observed at the same time, and, as
long as we take care to only advance one release branch at a time, we
can easily keep track of each of them. This is what this PR does.
This required a few changes to our release process. Most notably:
- Obviously, as this is the main point of this PR, the build process has
once again been restricted to only trigger new releases from the
`master` branch.
- As our CI machinery cannot easily be made to produce multiple releases
from a single build, the `check_for_release` step will only recognize
a commit as a release trigger if it changes a single line in the
`LATEST` file. This restriction comes in addition to the existing one
that a release commit is only allowed to change either just the
`LATEST` file or both the `LATEST` and
`docs/source/support/release-notes.rst` files.
- The docs publication process has been changed to update _all_
published versions to display the _latest_ release notes page. This
means that the release notes page will always show you all published
versions, regardless of which version of the documentation you're
looking at. This also means that interleaving release notes correctly on
that page is a manual exercise.
- As per the intention of the new process, the `LATEST` file has been
updated to contained all existing post-1.0 stable releases. It should
also include all existing snapshot releases should we have more than one
at a time (say, should we discover an issue with 1.1.1 that required us
to work on a 1.1.2).
- The `release.sh` script has been dramatically simplified as I felt it
was trying to do too much and porting its existing functionality to a
multi-line `LATEST` file would be too hard.
CHANGELOG_BEGIN
CHANGELOG_END
2020-05-19 20:18:10 +03:00
|
|
|
7e448d810c1134c39afa2c555e85964b68976446 1.1.1
|
|
|
|
|
160936905d393a6f8fb35ea02ad6b3c401820dad 1.0.1
|
|
|
|
|
f050da78c9c8727b889bdac286156f19e2f938c4 1.0.0
|
