Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
update instructions (Ensure compatibility with K2forJ4 by setting max…
…imum K2 rollup release to prevent conflicts that can be caused by new features.)
- Loading branch information
30dc286
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the need for this commit. What do you see as the principle difference between these two lines, @eworkers ?
Can you please answer my question? -
#62 (comment)
30dc286
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to make sure in case k2 official version committed something not to break K2forJ4 for users who recently tried to upgrade to K2forJ4
example: recently K2 added description to tag, new commers to K2forJ4 followed the instructions and ended up with no value error for Tag description when trying to create a new tag