We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
make sure all downward dependecies have the stable cadence updates done, so that our feature/stable-cadence branch is updated appropriately.
feature/stable-cadence
As discussed, we're going to move flow-cli to v2 for this change, as this would make most sense with the semver guidelines.
flow-cli
v2
The process moving forward would be any updates to feature/stable-cadence we will update to v2, so pre-draft releases will look liike
v2.0.0.stable-cadence.1 v2.0.0.stable-cadence.2 v2.0.0.stable-cadence.3 ...
instead of currently where it is
v1.X.stable-cadence V1.Y.stable-cadence ...
The text was updated successfully, but these errors were encountered:
this PR starts the migration of flowkit out of the cli, so that we can have a separate v2 feature branch for stable cadence
flowkit
#1373
Sorry, something went wrong.
ianthpun
No branches or pull requests
make sure all downward dependecies have the stable cadence updates done, so that our
feature/stable-cadence
branch is updated appropriately.As discussed, we're going to move
flow-cli
tov2
for this change, as this would make most sense with the semver guidelines.The process moving forward would be any updates to
feature/stable-cadence
we will update tov2
, so pre-draft releases will look liikev2.0.0.stable-cadence.1
v2.0.0.stable-cadence.2
v2.0.0.stable-cadence.3
...
instead of currently where it is
v1.X.stable-cadence
V1.Y.stable-cadence
...
The text was updated successfully, but these errors were encountered: