-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(release): migrate to new app version scheme #306
Conversation
Align all our application versions that range between 0.x.x and 36.x.x with different semantics to a single version scheme with distinct semantics for what constitutes a breaking change. We have chosen to bump to v100.0.0 to signify the depature from the old version scheme to the new. For more information: dhis2/notes#293 BREAKING CHANGE: App version becomes decoupled from DHIS2 versions, see the d2.config.js or App Hub for DHIS2 version compatibility.
06ac11c
to
e146e13
Compare
🚀 Deployed on https://pr-306--dhis2-reports.netlify.app |
This does not seem to have the updated workflow for releasing to App Hub? |
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.
File changes look good to me
Updated code style, workflows, etc. Should be OK now. |
🚀 Deployed on https://pr-306--dhis2-reports.netlify.app |
Align all our application versions that range between 0.x.x and 36.x.x
with different semantics to a single version scheme with distinct
semantics for what constitutes a breaking change.
We have chosen to bump to v100.0.0 to signify the depature from the old
version scheme to the new.
For more information:
dhis2/notes#293
BREAKING CHANGE: App version becomes decoupled from DHIS2 versions, see
the d2.config.js or App Hub for DHIS2 version compatibility.