fix: update package version number #58
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The version number was omitted in the previous commit by mistake. This commit updates the version number. Because a release for version 2.0.2 was already created and published, while the package version was set to `2.0.1`, version 2.0.2 can no longer be used, because it's tied to that commit. For this reason, this commit skips version 2.0.2 and goes straight to 2.0.3.
MichaelRoytman
force-pushed
the
michaelroytman/update-version
branch
from
de16306
to
45fde49
Compare
ilee2u
approved these changes
Jan 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Jira: None.
The version number was omitted in the previous commit by mistake. This commit updates the version number. Because a release for version
2.0.2was already created and published, while the package version was set to2.0.1, version2.0.2can no longer be used, because it's tied to that commit. For this reason, this commit skips version2.0.2and goes straight to2.0.3.