-
Notifications
You must be signed in to change notification settings - Fork 677
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
Minor event dispatcher updates #2050
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge asap pls ❤️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you @kantai!
# [0.30.0](v0.29.5...v0.30.0) (2020-11-12) ### Bug Fixes * bump nodejs version in github workflow ([0640790](0640790)) * stub response for `/new_burn_block` (allows sidecar to run with latest core node) ([4a48a29](4a48a29)) ### Features * add locked STX events and balance info to tx and address endpoints [#282](#282) [#268](#268) ([67cb65d](67cb65d)) * add STX lock events to API endpoints ([e20f4df](e20f4df)) * integrate Stacking STX into database and provide through account API details, upgrade to nodejs v14 ([b61129c](b61129c)) * integrate stx lock event handling into db ([334eb9d](334eb9d)) * use core event_index from stacks-network/stacks-core#2050 ([9d8db70](9d8db70)) * use STX locked_address from stacks-network/stacks-core#2050 ([ac741d7](ac741d7))
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
locked_address
field to stx_lock_eventType of Change
Does this introduce a breaking change?
No.
Are documentation updates required?
No -- the sample event payload in
event-dispatcher.md
has been updated.