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

Feature: Switch v1.4.1 to released #248

Merged
merged 1 commit into from
Jul 6, 2023
Merged

Feature: Switch v1.4.1 to released #248

merged 1 commit into from
Jul 6, 2023

Conversation

mmv08
Copy link
Member

@mmv08 mmv08 commented Jun 28, 2023

This PR:

  • Switches the released flag for 1.4.1 to true
  • Adjusts tests that checked that the latest returned version was 1.3.0

@mmv08 mmv08 requested review from a team as code owners June 28, 2023 11:25
Copy link
Member

@rmeissner rmeissner left a comment

Choose a reason for hiding this comment

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

What impact does this have on the interface that use this (i.e. Safe Wallet)? Would they start creating Safes with the new version?

@mmv08
Copy link
Member Author

mmv08 commented Jun 30, 2023

@rmeissner:

We have a global constant (set to 1.3.0) that we filter by. However, some places just filter by network. We could ensure everywhere relevant uses the constant and/or the released flag though.

That's their latest update from 3 months ago. I will double check with the web team before releasing

@katspaugh
Copy link
Member

This is definitely a breaking change for us. Should have been a major version, not a patch version. I've fixed it in the linked PR for multisends. Need to check other contracts too.

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.

3 participants