bump package versions for ephesus#4607
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
zeeshanakram3
left a comment
There was a problem hiding this comment.
- Shouldn't we also bump
query-nodeversion? Here is the list of all versions we selected for ephesus release
- After Joystream/hydra#516 has been merged, and new hydra version released, we should also update the hydra dependencies in the QN
Thank you I was looking for this to cross check. Will revise to match.
Noted |
|
There are a couple of PRs updating joystream-js package, so I assume that will need to be bumped also and published to npm eventually? @zeeshanakram3 |
I talked to Theo about the PR that he created, and he said that merging it is not important as they have found workaround for it. The other one should be merged I believe as this will be required for Apps. So yes, newer version of joystream-js package should be published to npm |
cli/package.json
Outdated
| "name": "@joystream/cli", | ||
| "description": "Command Line Interface for Joystream community and governance activities", | ||
| "version": "0.10.0", | ||
| "version": "0.11.0", |
There was a problem hiding this comment.
I'm wondering if we should bump versions of all packages that still start with 0. to 1. now that we're on mainnet,
There was a problem hiding this comment.
1.0.0 - mainnet
1.1.0 - apps
1.20 - ephesus
There was a problem hiding this comment.
If you mean 1.2.0 for Ephesus then sounds good.
tests/network-tests/package.json
Outdated
| "@apollo/client": "^3.2.5", | ||
| "@joystream/distributor-node-client": "^0.2.0", | ||
| "@joystream/types": "^0.20.6", | ||
| "@joystream/types": "^0.20.7", |
There was a problem hiding this comment.
Same comment as w.r.t. @joystream/cli, it looks strange to not have the patch version at all and only update the minor one during a new release.
There was a problem hiding this comment.
So we go for 0.21.0 for ephesus, unless we want to also start at 1.0.0 for mainnet, so making ephesus version 1.1.0 (as there are no runtime changes for apps release)
There was a problem hiding this comment.
I think we should start at 1.0.0 for mainnet for consistency
cli/package.json
Outdated
| "@ffprobe-installer/ffprobe": "^1.4.1", | ||
| "@joystream/metadata-protobuf": "^2.5.0", | ||
| "@joystream/types": "^0.20.6", | ||
| "@joystream/metadata-protobuf": "^2.7.0", |
There was a problem hiding this comment.
There will be apps release before ephesus and 2.6.0 is already taken, so I think 2.7.0 should be the apps and 2.8.0 - Ephesus?
There was a problem hiding this comment.
That's a sensible suggestion.
query-node/mappings/package.json
Outdated
| { | ||
| "name": "query-node-mappings", | ||
| "version": "0.1.0", | ||
| "version": "1.0.0", |
There was a problem hiding this comment.
Another question is whether we should bump the major version already for the apps release or for Ephesus? Otherwise we'd have to use something like 0.1.2 for the apps release.
There was a problem hiding this comment.
Sounds good to me. With reference to bumping version on master #4616 (review) lets make it
1.0.0 for master branch,
1.1.0 for apps release,
1.2.0 for ephesus?
|
Bumped versions to also take into consideration incoming PR to master #4560 |
Lezek123
left a comment
There was a problem hiding this comment.
- CLI/network-tests should depend on
@joystream/jsof version at least1.3.0(currently^1.0.0) - W.r.t.
@joystream/types, I think the combination of using^1.1.0and bumping only the minor version during an upgrade like Ephesus is risky. We should probably either bump the major version when there are non-backward-compatible changes (like the removal of sudo pallet, changes in existing event parameters etc.) or use~1.1.0to avoid some of our apps using non-compatible version of@joystream/typesin the future.
|
|
Updated as suggested. You will note I had to bump the dependency in migration-scripts as well, although that set of migration scripts should all be dropped, in addition to some in api-scripts as they depend on sudo. I will prepare a separate PR for that. |

Bump package versions to be higher than master branch.
┆Issue is synchronized with this Asana task by Unito