-
Notifications
You must be signed in to change notification settings - Fork 12
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
refactor: add option to generate unsigned tx for publishing package #65
Conversation
Code Coverage SummaryClick to see the summary
Click to see the extended report
|
scripts/publish-package.js
Outdated
requestType: 'WaitForLocalExecution', | ||
}); | ||
if (publishTxn.effects?.status.status !== 'success') throw new Error('Publish Tx failed'); | ||
if (!options.offline) { |
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.
what's the use case for offline support for publishing packages? similar to evm, i don't see why we're offline signing deployments as opposed to other txs. I'm ok to add it since it's a small change and it's already ready, but otherwise best to avoid spending time on use cases we don't need
functionality has been moved into TS scripts on main, this needs some refactor |
Co-authored-by: Milap Sheth <[email protected]>
Closing this and created this pr #70 for changes as per typescript |
https://axelarnetwork.atlassian.net/browse/AXE-4129
Needed a new function to return module dependencies and bytecode.