Skip to content
New issue

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

Stable Cadence Installation Workflow #1374

Closed
gregsantos opened this issue Feb 2, 2024 · 0 comments · Fixed by #1410
Closed

Stable Cadence Installation Workflow #1374

gregsantos opened this issue Feb 2, 2024 · 0 comments · Fixed by #1410
Assignees

Comments

@gregsantos
Copy link
Contributor

gregsantos commented Feb 2, 2024

The current workflow of supporting stable cadence overrides the existing flow-cli binary

https://forum.flow.com/t/update-on-cadence-1-0/5197/7

Until Stable cadence is offically out and we stop supporting anything before (v1.X deprecation), we will have a new workflow that can allow both binaries to exist at once.

A solution to that would be having a flow and flow-sc binary that is created, and that flow-sc is going to use the latest pre-release version of flow-cli at v2.0.0.stable-cadence.X, which will always have the latest changes on master, but with the breaking stable cadence changes

@gregsantos gregsantos converted this from a draft issue Feb 2, 2024
@gregsantos gregsantos moved this from 🧊 Backlog to 🔖 Ready for Pickup in 🌊 Flow 4D Feb 2, 2024
@ianthpun ianthpun moved this from 🔖 Ready for Pickup to 🏗 In Progress in 🌊 Flow 4D Feb 2, 2024
@jribbink jribbink moved this from 🏗 In Progress to 👀 In Review in 🌊 Flow 4D Feb 15, 2024
@jribbink jribbink assigned jribbink and unassigned ianthpun Feb 15, 2024
@github-project-automation github-project-automation bot moved this from 👀 In Review to ✅ Done in 🌊 Flow 4D Feb 26, 2024
@gregsantos gregsantos moved this from ✅ Done to Closed (Cycle 2) in 🌊 Flow 4D Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants