(chore) Release v5.2.2 #182
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
jayasanka-sack
force-pushed
the
v5.2.2
branch
from
19889a2
to
2ab6aa1
Compare
vasharma05
approved these changes
Feb 9, 2024
|
Yayyy 👏 |
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.
This resolves the issue discussed here: openmrs/openmrs-distro-referenceapplication#782 (comment).
The reason the package didn't get pushed to the registry is that there was no overridden release command, which resulted in only the version number in the root package.json file being incremented.
I renamed
ci:releasetoreleaseas there was no usage ofci:releasefound.