Prepare for cmcc 12 #12
Conversation
uwilken
force-pushed
the
prepare-for-cmcc-12
branch
3 times, most recently
from
ddde6ac
to
d1a5d46
Compare
uwilken
force-pushed
the
prepare-for-cmcc-12
branch
from
d1a5d46
to
4e7ae8b
Compare
uwilken
force-pushed
the
prepare-for-cmcc-12
branch
from
480c822
to
9231dca
Compare
uwilken
force-pushed
the
prepare-for-cmcc-12
branch
from
9231dca
to
0f0e4e8
Compare
| "@jangaroo/runtime": "^1.0.0" | ||
| }, | ||
| "devDependencies": { | ||
| "@jangaroo/build": "^1.0.0", | ||
| "@jangaroo/core": "^1.0.0", | ||
| "@jangaroo/publish": "^1.0.0", | ||
| "@jangaroo/run": "^1.0.0", | ||
| "eslint": "7.27.0", | ||
| "rimraf": "^3.0.2" | ||
| "@jangaroo/build": "^1.5.0", | ||
| "@jangaroo/core": "^1.5.0", | ||
| "@jangaroo/publish": "^1.5.0", | ||
| "@jangaroo/run": "^1.5.0", |
There was a problem hiding this comment.
@aholtkamp While discussing updating cm versions in plugins we came across node, pnpm and jangaroo versions. We want to stay compatible with old cms releases as long as possible and avoid cms release specific maintenance branches.
Quest now is, if the version updates in the package.json are reasonable for you? We left the jangaroo/runtime version unchanged to stay compatible with older studio installations. All the other dependencies should be used to build the plugin artefact internally.
There was a problem hiding this comment.
For runtime only the normal "dependencies" are relevant. So this change looks good to me if we want to avoid having a maintenance branch while still being compatible to older cms releases.
Update libs
tested with master and 2310