Version 4.x - Migration to v3 #95
Conversation
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
salesfelipe
force-pushed
the
feature/migrationV3
branch
from
7862a83 to
2219e93
Compare
salesfelipe
force-pushed
the
feature/migrationV3
branch
from
44e2dd8 to
f445a41
Compare
salesfelipe
force-pushed
the
feature/migrationV3
branch
from
045d120 to
4dc9ccb
Compare
salesfelipe
force-pushed
the
feature/migrationV3
branch
from
68f874e to
5233190
Compare
| @@ -1,7 +1,7 @@ | |||
| { | |||
| "vendor": "vtex", | |||
| "name": "my-subscriptions", | |||
| "version": "1.14.2", | |||
| "version": "3.14.2", | |||
There was a problem hiding this comment.
@salesfelipe why not bumping to 2.x here? Is it already in use?
There was a problem hiding this comment.
Yes, the portal version(current 0.x) will become the 2.x and the storev2 version(currently 1.x) will be the 4.x
There was a problem hiding this comment.
Okay. Guess that will be written down in the readme right?
There was a problem hiding this comment.
Now it will :harold_pain:
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What does this PR do? *
How to test it? *
[email protected]in workspaceRelated to / Depends on *
https://github.com/vtex/subscriptions-graphql/pull/63