Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/1.2.0 #177

Merged
merged 27 commits into from
Jul 7, 2021
Merged

Release/1.2.0 #177

merged 27 commits into from
Jul 7, 2021

Conversation

marcelosalloum
Copy link
Contributor

@marcelosalloum marcelosalloum commented May 28, 2021

Changelog

  • SEP-06 now supported
  • SEP-08 now supported
  • Fixed a bug when overriding home domain
  • Fixed an issue where balance amounts were being overwritten
  • Sending to Muxed Accounts is now supported

marcelosalloum and others added 12 commits May 24, 2021 12:08
### What

Revert "Disable support to SEP-8 payments (#166)": 15ca900.

Additionally, includes human readable string for Horizon's message `op_not_authorized`.

### Why

We had temporarily removed it in PR #166 to better organize our releasing setup.
### What

Support SEP-8 "Action Required" flow.

Closes #113 

### Future Work

The action fields received in the action required responses are all being handled as strings for now. I'll update this behavior to accept different kinds of inputs in the future, since the [SEP-9] field types can include "string", "country code", "phone number", date", "number" or "binary".

[SEP-9]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md

### Screenshot

https://user-images.githubusercontent.com/1952597/119165154-958bd600-ba33-11eb-9639-3d014c8003d4.mov

### How to test

Use the jenkins preview link with `/account?secretKey=SBQZPYFQNQD4B7MP7PC3NKCMS5G5LD6PVO7BUYC34M4BBFN6KCXSKSVD` and send a small payment to `GBID36ML6VVNPIF6SQATQW5QIBREQAVEHQIUMWDLQCSVIYX2IJGK4KPP`.

#### KYC Approval Criteria

* Emails starting with "x" will get rejected
* Emails not starting with "x" will get approved.

If you need to repeat your tests you might need to delete the KYC already stored in the server with:
```curl
curl -X DELETE https://sep8-server.dev.stellar.org/kyc-status/GASA5HCKMDAPLB6NIV7ADDA6YMTAQ2555TXKMS7FSVO44TJXHEGXLICZ
```
* add Sep-6 deposit flow

* fix typo

* adding bad input handling for deposit choice

* reorder import

* rm unneeded eslint disable

* memoize depositTypes choices

* PR comments
* add Sep-6 deposit flow

* fix typo

* adding bad input handling for deposit choice

* reorder import

* rm unneeded eslint disable

* memoize depositTypes choices

* PR comments

* Add withdraw flow for sep-6

* rm console logs

* update sep6 schemas to match other sep's

* PR comments
* GitHub link in footer

* Remove announcement banner
### What

Add instructions to Test SEP-8 Payments in the Demo Wallet using our SEP-8 reference server sep8-server.dev.stellar.org.

Closes #160
* upgrading stellar-sdk and adding optional muxed acct support

* update TransactionBuilder to use new params
* add Sep-6 deposit flow

* fix typo

* adding bad input handling for deposit choice

* reorder import

* rm unneeded eslint disable

* memoize depositTypes choices

* PR comments

* Add withdraw flow for sep-6

* rm console logs

* first pass at claimable balance for deposit

* update sep6 schemas to match other sep's

* add withdraw claimable balance path

* add amount field to withdraw

* add untrusted asset flow

* add better message for withdraw flow

* rm console logs

* rm unneeded dep and const explanation

* rm unneccessary check

* rm <InfoBlock> and replace with <div>
### What

Fix SEP-8 action_required return condition.

### Why

The code was using the wrong condition check.
…se (#175)

### What

Support all SEP-9 fields when handling SEP-8 "action_required" response.

### Why

In order to have a complete implementation of SEP-8 we should be able to send binary and date fields as well.
### What

Support SEP-8 "action_required" responses with GET action methods.

### Why

We were only supporting SEP-8 responses with POST action methods, which is not the default response according with the SEP.
@marcelosalloum marcelosalloum marked this pull request as draft May 28, 2021 14:53
@stellar-jenkins
Copy link

marcelosalloum and others added 6 commits June 4, 2021 15:31
### What

Add description explaining the Demo Wallet keypair represents the Sending Anchor when we're demo-ing SEP-31. Added to Readme.md and to the SEP-31 modal.

### Why

In all other use cases for the Demo Wallet, the keypair actually represents a client's account, SEP-31 is the only exception.
* Sentry: do not trace any origin (localhost CORS issue) (#182) (#183)

* Update Sentry tracingOrigins
…ing" response (#187)

### What

Fix log when receiving an empty (or "0") timestamp from a SEP-8 "pending" response.

### Why

It's possible to receive `timestamp: 0` from a "pending" SEP-8 response and we were not handling that case. Ref: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md#pending
@stellar-jenkins
Copy link

quietbits and others added 3 commits June 24, 2021 10:13
@stellar-jenkins
Copy link

quietbits and others added 3 commits June 25, 2021 11:52
* Do not show actions for untrusted regulated assets

* Add extra check
* SEP-6 deposit amount added

* SEP-6 deposit start polling button

* Text updates

* Change deposit success modal title
@stellar-jenkins
Copy link

### Changes

* After getting the KYC approved, send the user straight to the “review & submit” modal.
* Update the “Review & Submit” modal text to “`KYC has been approved.` Please review the updated operations before submitting your SEP-8 payment.”
* Update the log message when resubmitting payment automatically.

### Preview

https://user-images.githubusercontent.com/1952597/124181606-1ce55400-da8c-11eb-8fb3-3c8adb917f13.mov
Addition to SEP-08 instructions and added to the roadmap
@marcelosalloum marcelosalloum changed the title [DO NOT MERGE] Release/1.2.0 Release/1.2.0 Jul 7, 2021
@marcelosalloum marcelosalloum marked this pull request as ready for review July 7, 2021 19:55
* Updated readme with release notes
	modified:   README.md

* Reversed the order for release notes
Copy link
Contributor

@shanzzam shanzzam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good for release!

@marcelosalloum marcelosalloum merged commit 790e8ba into master Jul 7, 2021
@marcelosalloum marcelosalloum deleted the release/1.2.0 branch July 7, 2021 20:38
@marcelosalloum marcelosalloum restored the release/1.2.0 branch July 8, 2021 13:54
marcelosalloum added a commit that referenced this pull request Jul 19, 2021
marcelosalloum added a commit that referenced this pull request Jul 19, 2021
### What

Reverts commit 790e8ba and PR #177.

### Why

We should merge release branches into master using `rebase & merge` instead of ~`squash & merge`~ so we can maintain a proper history and correctly identify the developer responsible for this or that code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants