Skip to content
This repository has been archived by the owner on Apr 15, 2019. It is now read-only.

Bundle correct version of lisky / lisk-commander with 1.x releases #291

Closed
fchavant opened this issue Jun 22, 2018 · 4 comments
Closed

Bundle correct version of lisky / lisk-commander with 1.x releases #291

fchavant opened this issue Jun 22, 2018 · 4 comments
Assignees
@fchavant
Labels
bug
Milestone
Version 1.0.0

Comments

@fchavant
Copy link
Contributor

Betanet releases have been shipped with lisky 0.3.0 which is not compatible with the 1.0 API.
@fchavant fchavant added the bug label Jun 22, 2018
@fchavant fchavant added this to the Version 1.0.0 milestone Jun 22, 2018
@fchavant fchavant self-assigned this Jun 25, 2018
@fchavant
Copy link
Contributor Author

@shuse2 said to use lisk-commander@beta

@fchavant fchavant mentioned this issue Jun 25, 2018
Merged
@Nazgolze
Copy link
Contributor

Closed by #293

@fchavant
Copy link
Contributor Author

lisk-commander 1.0.0-rc.0 is released on npm, please this version to bundle
it can be installed by npm i -g --production [email protected] or npm i -g --production lisk-commander@next

@fchavant fchavant reopened this Jun 25, 2018
@fchavant fchavant reopened this Jun 25, 2018
@fchavant
Copy link
Contributor Author

The binary was renamed fromlisky to lisk; the question is whether the top-level symlink can be removed. @Nazgolze @karmacoma

Nazgolze added a commit that referenced this issue Jun 25, 2018
@Nazgolze
Merge pull request #297 from LiskHQ/291-use-lisk-commander
7fc8630 
Remove top-level lisky symlink  - Closes #291
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@fchavant fchavant

Labels
bug
Projects
None yet
Milestone
Version 1.0.0
Development

No branches or pull requests
2 participants
@Nazgolze @fchavant