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.

Sign up for GitHub

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

Jump to bottom

chore(legacy-core): document tag revert method for deployment of contracts v1 #104

Open
Tracked by #76
mfw78 opened this issue Jun 3, 2024 · 2 comments
Open
Tracked by #76

chore(legacy-core): document tag revert method for deployment of contracts v1 #104

mfw78 opened this issue Jun 3, 2024 · 2 comments
Assignees
@fedgiac
Labels
E:5.2 Contracts migrations See https://github.com/cowprotocol/pm/issues/32 for details

Comments

@mfw78
Copy link
Contributor

mfw78 commented Jun 3, 2024

No description provided.

@mfw78 mfw78 mentioned this issue Jun 3, 2024
Open
22 tasks
@mfw78 mfw78 added the E:5.2 Contracts migrations See https://github.com/cowprotocol/pm/issues/32 for details label Jun 3, 2024
@mfw78 mfw78 transferred this issue from cowprotocol/pm Jun 3, 2024
@fedgiac fedgiac self-assigned this Jun 10, 2024
@mfw78
Copy link
Contributor Author

mfw78 commented Jun 20, 2024

Confirm that we are't going to proceed with this, and instead have documented the procedure for tag reversion for subsequent deployment of legacy contracts if required?

@fedgiac
Copy link
Contributor

fedgiac commented Jun 20, 2024

Confirmed.

@mfw78 mfw78 closed this as completed Jun 20, 2024
@mfw78 mfw78 reopened this Jun 20, 2024
@mfw78 mfw78 changed the title chore(legacy-core): forge deployment scripts for specific contracts v1 chore(legacy-core): document tag revert method for deployment of contracts v1 Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fedgiac fedgiac

Labels
E:5.2 Contracts migrations See https://github.com/cowprotocol/pm/issues/32 for details
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mfw78 @fedgiac