(chore) Release v17.0.0 #154
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
denniskigen
requested review from
donaldkibet,
icrc-psousa,
icrc-jofrancisco and
ibacher
ibacher
approved these changes
Aug 29, 2024
|
This might be one of the biggest version number leaps in OMRS history. |
|
Brave new world |
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.
Requirements
Summary
This PR cuts a new major release of the Angular Form Engine with a breaking change following an Angular version upgrade (from v16 to v17). Note that the proposed version number is v17.x.x to align with the Angular library ecosystem convention of aligning version numbers with the Angular version.
Screenshots
Related Issue
Other