fix: use version key for master install in zvm #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces a critical update to the Zig Version Manager (zvm) that resolves an issue with the installation of the
master
version of Zig. Previously, when attempting to install themaster
version, zvm would not correctly utilize the version key provided in the JSON configuration, leading to installation failures. With this update, zvm now correctly references theversion
key formaster
, ensuring that the unique development version of Zig is accurately fetched and installed.Changes
fetchVersionData
function to use theversion
key in the JSON configuration when installing themaster
version.master
version is requested, and if so, to use the unique version identifier provided by the JSON configuration.Impact
master
version of Zig without encountering theEmptyVersion
error.Notes
This fix is crucial for developers who rely on the cutting-edge features of Zig and need to work with the latest development builds. The zvm's reliability is significantly improved, promoting a smoother development experience for the Zig community.
Closes #17