Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Releases of Voyager should identify which testnet(s) they work on
See original GitHub issueUI Version: develop
Description: I think that version 0.9.x of Voyager functioning with gaia-8000 doesn’t make much sense. Wouldn’t it be better if we just publicly labeled this release as Voyager 8000?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:18 (8 by maintainers)
Top Results From Across the Web
Releases of Voyager should identify which testnet(s) they ...
i would propose we stick with semver for testnets and after mainnet launch. let's just change the title of the release for the...
Read more >Voyager Update — v0.5.0 Release - Cosmos Blog
Voyager is your friendly user interface to interact with the Cosmos Network. ... We are working hard on re-enabling testnet support for the...
Read more >Ethereum launches testnet for Shanghai upgrade
The upgrade introduces an crucial change to Ethereum Virtual Machine (EVM), the technology behind the network smart contracts.
Read more >Etherscan Set to 'Deprecate' Ethereum's Ropsten and Rinkeby ...
The process of phasing out Ethereum's Ropsten and Rinkeby test networks (testnets) starts Wednesday when blockchain explorer Etherscan shuts ...
Read more >Ethereum Launches Testnet to Begin Work on Shanghai ...
The Ethereum Foundation on Friday announced the launch of a pre-Shanghai testnet it's calling “Shandong.” Shandong will serve as a testing ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Sounds reasonable. Just brainstorming: Can we use funky semver by putting the network number in there? Like 0.8001.1. After 1.x we could change that again.
we would switch back to semver I suppose