release 1.18.0-snapshot.20211109.8328.0.92181161 (#11623)
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.
@remyhaemmerle-da is in charge of this release.
Commit log:
```
92181161cc2d7b7f6d036ab90b1d9a5dd4c4656c LF: Abstract VersionedValue and VersionedContractInstance (#11533)
b87acab897998cd4f7eef9c3d2191fc0ac52bcdb foldLeft, foldRight, other Foldable specializations (#11592)
92dfcdeb243b76d47621e6f9ff30b76a23bd8392 [Self-service error codes] Use error validators in ApiPackageManagementService (#11575)
6372d41d1302b3d294c3ea99095e920fc4c6ef28 limit contract insertion/deletion batching on backpressure (#11589)
3588284fad206096653bf225c919d3fb04850529 Fix screenshots in daml intro 2 (#11617)
ef3fc0ef4b942b195045a5674e03531ace573ce8 Cache type synonym expansion in safeToReexport (#11612)
70b2fe35342008fb046a5cf8cc051d0663426f0c Provide byInterface fields for fetch, exercise. (#11607)
830779ff787f1683d53ce4827a8ce4266fdf4c6f LF: drop useless class com.daml.lf.transaction (#11601)
7c92cabff7716c9f636f565e7d37e84d60160917 Cache type synonym expansion in isDuplicate (#11611)
cfd521ff86d2266523b56b9442033c9c882f8c47 Fix GHC build errors on macOS (#11560)
a7559d047ea98e8590a50c48200057f4783b34da LF: Rename GenTransaction to Transaction (#11599)
3b61a1b74851d70d6b621be29126bd1fde35e600 LF: allow exercise command by template for inherited choice. (#11584)
af1bee7b821f89eca687f50f66e44ccb2bd7c6f1 precondition lf conversion (#11538)
f722cf13cda26fe1bb573004416ac944cf334789 Bump extractor init timeout to 60s (#11598)
1e0a221379d79f1d2e302cdee9d3f6991538d20a Set symlink_node_modules = False (#11606)
ac19c8cff56b007dd5d8a56c664d326c54bf8a50 Synchronize in multi-participant script tests (#11594)
dd1b0347eca16afb811dcb175086aa73d57aeacb Restart the submission interpretation in case of a race [DPP-737] (#11579)
8d2b1b9ffeea6374cd7762307dbd0eb3d820ceb5 [JSON-API] Port of http-perf-test to sandbox(aka next) (#11543)
56a6db8f73dcd9ab41bae54793dcadba8b219efe codeowners: reflect change in onwership of meiersi-da (#11505)
d4336510af63dd7febeafa0a8caf6f837da24491 fix a few typos in Daml-LF spec (#11583)
5dee88b038fdb6ef0938720f99a495fb6a3299b9 Refactoring store factories [DPP-709] (#11572)
41fb2890d6a7effa532950f201baa6e226860ac6 Port LedgerApiServer rate limiter interface from canton (#11577)
04cc5d7a76725acd6d1d4bc6bf60a9d97ffa33d1 Mark JSON API integration tests as flaky (#11586)
3bed7a9b4f921b9e0ad972edcccf5d87c2ef1522 Drop unused defaultFeatureFlags (#11580)
cbc3c8c68674478dfa0c1e43d4f41b09a21750a2 Add by_interface field in Create, Fetch, & Exercise transaction nodes. (#11576)
7d68e05f7f0e0d8784bf1102ff11aaf1c0374c82 Remove virtual choices (#11482)
9b94fa97699b5210a19403c01cf77069eec8ec1c [ledger-api] - metadata for invalid deduplication period [KVL-1170] (#11534)
e7eb60f087caf4670769c2d3117916e1438469cd update compat versions for 1.18.0-snapshot.20211102.8257.0.7391a3cd (#11531)
a3d04cafafd11382ffd312b9c0eb06d2d698ddcb Migrate matches-docs tests to sandbox on postgres (#11573)
21c97453bd5370bfaeec69afece2ec56659ef304 [Self-service error codes] ValueSwitch parameterized method (#11567)
6a0b84e3d042645767eebd0fea6cbceb22c96904 Run Script export tests against BR (#11574)
a3195fd62decf56625190eb6b2ab2d69f1f0c243 fix link to blog (#11570)
08236012af6348057ec27c43815e6809766c784b Self-service errors: generate error deprecation docs [KVL-1187] (#11539)
8d48cf669d6314214be17851f0ec12ea04619da1 DPP-664 Create contracts in batches (#11515)
9ef2eaf8037fbaaacef692442f4f1f0ffd4d6956 Remove parameter table join from SQL queries [DPP-705] (#11562)
af7f7f3f01c9d516ed819e2f95acccebadd37626 Fix LF coedowners (#11563)
445031114fe87b94c15fcae7f1aa254a63ce9b04 Exclude/fix compatibility tests (#11529)
699c28f59ec388059f7b34bb439dc774bd1a7cf5 rotate release duty after 1.18.0-snapshot.20211102.8257.0.7391a3cd (#11522)
4d4869f06ed5b6465549fc323839d96ab165670b interfaces: Improve fixed choice lookup (#11551)
ba96bf784c76b481533077902de745b15b5618de Add DbDtoToStringsForInterning [DPP-708] (#11557)
692dac665d4659f1399a0f56478450c596bf318a LF: deprecate remaining type alias in Transaction (#11554)
7bc0f827330b906bbe2d9ca314583d27ba5df8ba [kvutils] - Extract command deduplication steps from the TransactionCommitter [KVL-1174] (#11547)
0e95ccb35483924df95b907bc12da47371f20ad5 Wire LedgerEndCache to relevant StorageBackend factories [DPP-704] (#11549)
73cb42e102b069222fa128c420877d2b225c8c9d LF: deprecate ensureNoCid and assertNoCid in CidContainer (#11502)
30bfee98228975e57360ff30dd573883d090ed0c Upgrade canton for conformance tests (#11550)
b84a9142d180c2b223ddefb205dbaf4e00174270 Extractor: replace `sandbox-classic`-based fixtures with `sandbox`-based ones (#11489)
d86fe92950ea4c66e661a05966980d7de5addfef ledger-api-bench-tool - flexible stream filters [DPP-667] (#11458)
214c7ab445c94c5730c62ace45c61aede7ecc446 Self-service errors: generate groups documentation [KVL-1186] (#11526)
60dc2869e777eb50e9bb8ccd005af07895e6d4e3 Avoid unnecessarily decoding DALFs during dependency installation (#11541)
afd79b6729a990341cec972297236f0ae25dc446 Improve logging for dependency installation (#11540)
fdde5353f4d83382a4bef90d9fdedc6dbb4b5881 fix hoogle by pinning nixpkgs (#11548)
5e93df6b521fe669baa2d7f859cc81f6bb60f6f6 Full conformance test with self-service error codes on ledger-on-memory (#11524)
efaf20b04206bcf66f22a95c37c895f52992df61 update NOTICES file (#11546)
c7bb94be6588680c293e48e8b92d2d8e9625b840 Modify contract key attribute age for createAndExercise to avoid contract key violation on slow running tests (#11530)
541d07c3a958f6c6319f2c52e76820e724bf5a25 Add string-interning data access [DPP-707] (#11484)
6c9416492d1241fb7130ec9450f4e40e8b1029d2 Switching to composition at StorageBackend [DPP-704] (#11520)
d006ad0e8b7619e7018d51a89b0b6002a520c207 Add string-interning view primitives [DPP-702] (#11475)
a917520851ece8eefa4cf0dbe343d2ebaba836c8 Save the submission time in the command deduplication value [KVL-1173] (#11509)
669186f118ff87eb7436fc5bb2841e325e90662b Add priority-queue based worker Source [DPP-717] (#11500)
2091f59aac847b297abf282d8908844df199c71f Remove cats from kvutils (#11537)
b83af37077d9e228b60312d71971cc4c9fb56bbc Fix recache log statement (#11536)
776790e38612922da715cd1e24e8a8b9575827bd Add choice collisions in scala name collision checker (#11528)
2efcb21f3e768f8960c832ee25324f6ba3c16143 Extract the setting of the time bounds on the commit context [KVL-1173] (#11516)
9bb1d6443cc32815e44a24ea39a15671f76c2ae4 [ledger-api] - Return FAILED_PRECONDITION gRPC status code for invalid deduplication duration [KVL-1170] (#11483)
c098d756210926e2dd4f0a844d6610a166c669ae Add a --log-level flag to damlc (#11514)
afee94858f1c9b91876139728b133f4ba2074180 Bump rules_nixpkgs (#11517)
d6fb67c71ecbb2e709a949820c8eab2548288ac3 release 1.18.0-snapshot.20211102.8257.0.7391a3cd (#11521)
ac49d69e13f6fd5506cedd97833ab02dba15d050 Ensure that -Werror converts parser warnings into errors (#11511)
bda35ca23458397f3c410127b4c842b10939575f ledger-offset: Add a conversion to ByteString. (#11491)
8a9f15b8de498ea0f209b4e3fae7144b5d9c0707 [DPP-686][Self-service error codes] Removing default error factories (#11403)
bb37eef1563e740fc4563d922d5af92b32521c7b Switch script & trigger tests to postgres-backed Sadbonx (#11525)
```
Changelog:
```
- [JSON API] While updating the contract table for a query, if the DB appears to be slow,
JSON API will slow down its own inserts and deletes at some point rather than construct
ever-larger INSERT and DELETE batch commands.
See `issue #11589 <https://github.com/digital-asset/daml/pull/11589>`__.
[Ledger API] Retry the interpretation of a command in case of a race
with other transactions. This fix drastically reduces the likelihood of the error
"Could not find a suitable ledger time after 0 retries".
[ledger-api] - Return max_deduplication_duration as part of the metadata sent with the gRPC status for commands rejected because of invalid deduplication periods
- [Integration Kit] - ledger-api-bench-tool - added flexible party and template filters for transactions, transaction trees and active contract streams
[ledger-api] - Return FAILED_PRECONDITION gRPC status code, instead of INVALID_ARGUMENT, for an invalid command deduplication duration
```
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Azure Pipelines Daml Build <support@digitalasset.com>
2021-11-10 12:33:02 +03:00
|
|
|
92181161cc2d7b7f6d036ab90b1d9a5dd4c4656c 1.18.0-snapshot.20211109.8328.0.92181161
|
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-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
|
