You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can no longer reference Paloma versions directly from Pigeon since we upgraded to a version higher than 1 due to the go mod versioning system. We will need to add a /v2 suffix to our Paloma go.mod, but I forgot to do this for 2.2.0.
The text was updated successfully, but these errors were encountered:
# Related Github tickets
- VolumeFi#2136
# Background
From v2 onwards, go forces us to either:
- create a new directory for every version and maintain all versions
within the codebase
- append the version to the module name
We opted for the latter since we don't want to support multiple paloma
versions.
# Testing completed
- [ ] test coverage exists or has been added/updated
- [ ] tested in a private testnet
# Breaking changes
- [ ] I have checked my code for breaking changes
- [ ] If there are breaking changes, there is a supporting migration.
We can no longer reference Paloma versions directly from Pigeon since we upgraded to a version higher than 1 due to the go mod versioning system. We will need to add a
/v2
suffix to our Palomago.mod
, but I forgot to do this for2.2.0
.The text was updated successfully, but these errors were encountered: