Skip to content

bump package versions for ephesus#4607

Merged
mnaamani merged 9 commits intoJoystream:ephesusfrom
mnaamani:ephesus-bump-package-version
Feb 21, 2023
Merged

bump package versions for ephesus#4607
mnaamani merged 9 commits intoJoystream:ephesusfrom
mnaamani:ephesus-bump-package-version

Conversation

@mnaamani
Copy link
Copy Markdown
Member

@mnaamani mnaamani commented Feb 7, 2023

Bump package versions to be higher than master branch.

┆Issue is synchronized with this Asana task by Unito

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 7, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated
pioneer-testnet ⬜️ Ignored (Inspect) Feb 21, 2023 at 0:07AM (UTC)

@mnaamani mnaamani changed the title bump packages version for ephesus bump package versions for ephesus Feb 7, 2023
Copy link
Copy Markdown
Collaborator

@dobertRowneySr dobertRowneySr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Copy Markdown
Contributor

@zeeshanakram3 zeeshanakram3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Shouldn't we also bump query-node version? Here is the list of all versions we selected for ephesus release

image

  1. After Joystream/hydra#516 has been merged, and new hydra version released, we should also update the hydra dependencies in the QN

@mnaamani
Copy link
Copy Markdown
Member Author

mnaamani commented Feb 8, 2023

  1. Shouldn't we also bump query-node version? Here is the list of all versions we selected for ephesus release

Thank you I was looking for this to cross check. Will revise to match.

After Joystream/hydra#516 has been merged, and new hydra version released, we should also update the hydra dependencies in the QN

Noted

@mnaamani
Copy link
Copy Markdown
Member Author

mnaamani commented Feb 8, 2023

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

@zeeshanakram3
Copy link
Copy Markdown
Contributor

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",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm wondering if we should bump versions of all packages that still start with 0. to 1. now that we're on mainnet,

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no objection.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.0.0 - mainnet
1.1.0 - apps
1.20 - ephesus

@Lezek123

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you mean 1.2.0 for Ephesus then sounds good.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, typo there :)

"@apollo/client": "^3.2.5",
"@joystream/distributor-node-client": "^0.2.0",
"@joystream/types": "^0.20.6",
"@joystream/types": "^0.20.7",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member Author

@mnaamani mnaamani Feb 13, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a sensible suggestion.

{
"name": "query-node-mappings",
"version": "0.1.0",
"version": "1.0.0",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good! 👍

@mnaamani
Copy link
Copy Markdown
Member Author

Bumped versions to also take into consideration incoming PR to master #4560

@mnaamani mnaamani requested a review from Lezek123 February 14, 2023 09:54
@sync-by-unito sync-by-unito bot closed this Feb 14, 2023
@mnaamani mnaamani reopened this Feb 16, 2023
Copy link
Copy Markdown
Contributor

@Lezek123 Lezek123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. CLI/network-tests should depend on @joystream/js of version at least 1.3.0 (currently ^1.0.0)
  2. W.r.t. @joystream/types, I think the combination of using ^1.1.0 and 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.0 to avoid some of our apps using non-compatible version of @joystream/types in the future.

@mnaamani
Copy link
Copy Markdown
Member Author

  1. CLI/network-tests should depend on @joystream/js of version at least 1.3.0 (currently ^1.0.0)

    1. W.r.t. @joystream/types, I think the combination of using ^1.1.0 and 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.0 to avoid some of our apps using non-compatible version of @joystream/types in the future.
  1. Well spotted
  2. That is a good point. Going with 2.0.0 sounds best.

@mnaamani
Copy link
Copy Markdown
Member Author

mnaamani commented Feb 21, 2023

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.

Copy link
Copy Markdown
Contributor

@Lezek123 Lezek123 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mnaamani mnaamani merged commit 8abfb11 into Joystream:ephesus Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants