corda/.ci
Andrius Dagys 0edfef2409 CORDA-696 - Create separate transaction types for contract upgrade transactions (#2589)
* CORDA-986 and CORDA-985 CompositeKey and Signature verification performance fixes (#2467)

* CORDA-696: Create separate transaction types for contract upgrade transactions.

Add rationale around upgrade transactions

Move contract upgrade transaction resolution logic into internal until it's stabilised.

Throw a better exception when contract attachment not found

Default legacy contract constraint to always accepting - needs to be changed to whitelist constraint before merging

Introduce a new upgraded contract interface that allows specifying the legacy constraint.

Remove StateLoader, make all tx resolution functions take in ServicesForResolution

Contract upgrade transactions can handle whitelist by zone constraints

When creating a contract upgrade transaction, make sure the attachment of the old cordapp gets attached when using hash constraints.
Attachment lookup for a given contract class name only scans currently loaded cordapps, and we don't load old versions of cordapps.

CORDA-696: Update upgrade docs
2018-02-26 11:29:25 +00:00
..
dependency-checker CORDA-351: force update dependencies and suppress vulnerabilities not… (#1944) 2017-10-26 12:16:57 +01:00
api-current.txt CORDA-696 - Create separate transaction types for contract upgrade transactions (#2589) 2018-02-26 11:29:25 +00:00
check-api-changes.sh CORDA-939 Modify Api Scanner to check api for internal exposures (#2510) 2018-02-14 16:42:56 +00:00
README.md Add README for our automated API check. (#1793) 2017-10-03 15:33:20 +01:00

!! DO NOT MODIFY THE API FILE IN THIS DIRECTORY !!

The api-current.txt file contains a summary of Corda's current public APIs, as generated by the api-scanner Gradle plugin. (See here for a detailed description of this plugin.) It will be regenerated and the copy in this repository updated by the Release Manager with each new Corda release. It will not be modified otherwise except under special circumstances that will require extra approval.

Deleting or changing the existing Corda APIs listed in api-current.txt may break developers' CorDapps in the next Corda release! Please remember that we have committed to API Stability for CorDapps.

!! DO NOT MODIFY THE API FILE IN THIS DIRECTORY !!