We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The find_best_semver_for_versions function seems to be matching on pre-release tags.
find_best_semver_for_versions
User reports say that the persistence network was reporting the following info before their upgrade today:
persistence
{ "type": "mainnet", "network": "persistence", "rpc_server": "https://rpc-persistence.architectnodes.com/", "rest_server": "https://api-persistence.cosmos-spaces.cloud/", "latest_block_height": 13870121, "upgrade_found": true, "upgrade_name": "v10", "source": "current_upgrade_plan", "upgrade_block_height": 13870350, "estimated_upgrade_time": "2023-11-02T14:34:22.177132", "upgrade_plan": { "height": 13870350, "binaries": [], "name": "v10", "upgraded_client_state": null }, "version": "v10.1.0", "error": null }
Notice v10.1.0. This was found in a pre-release tag:
We need to fix the find_best_semver_for_versions so it skips prerelease tags.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
find_best_semver_for_versions
function seems to be matching on pre-release tags.User reports say that the
persistence
network was reporting the following info before their upgrade today:Notice v10.1.0. This was found in a pre-release tag:
We need to fix the
find_best_semver_for_versions
so it skips prerelease tags.The text was updated successfully, but these errors were encountered: