Gregory Oschwald

It is now resolving pointers, which could fail. We are ignoring the error currently to prevent a breaking API change: https://github.com/oschwald/maxminddb-golang/blob/8b6ffca7d066a42285ca5ffc20668a462cb8ec32/internal/decoder/decoder.go#L359-L385

So that they are serialized to JSON as they appear in the database. This is unfortunately a breaking change and will need to wait until v3.

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change

## Summary - Updates Dependabot cooldown from 4 days to 7 days - Addresses zizmor `dependabot-cooldown` finding ## Test plan - [x] zizmor reports no cooldown findings after change