try gorm upgrades again

[mayberryzane]

Summary

• first go dependency upgrade upgrade go dependencies #7937 was hanging during db migration because gorm was attempting to convert some integer columns to bigint. now that those are overridden by an integer struct tag, planning to merge in these dependency upgrades again

How did you test this change?

• tested locally by auto-migrating from previous version and in a fresh install to make sure both worked

Are there any deployment considerations?

• no

Does this work require review from our design team?

• no

[changeset-bot]

⚠️ No Changeset found

Latest commit: ac684fd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

💥 An error occurred when fetching the changed packages and changesets in this PR

Some errors occurred when validating the changesets config:
The package or glob expression "@highlight-run/rrdom" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrdom-nodejs" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrweb" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrweb-player" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrweb-snapshot" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrweb-types" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "@highlight-run/rrweb-web-extension" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.
The package or glob expression "rrvideo" is specified in the `ignore` option but it is not found in the project. You may have misspelled the package name or provided an invalid glob expression. Note that glob expressions must be defined according to https://www.npmjs.com/package/micromatch.

[SpennyNDaJets]

LGTM!

Are there any deployment considerations?

Do we need a rollout/rollback strategy incase anything goes wrong?

[mayberryzane]

LGTM!

Are there any deployment considerations?

Do we need a rollout/rollback strategy incase anything goes wrong?

GORM automigrate won't do anything that would cause data loss, the biggest risk is an accidental DDL change that affects performance. Will be monitoring the rollout - if there are issues, we will revert ASAP to automigrate back to the original state. If there are issues after that, we have daily snapshots and can manually look at the delta to apply schema changes to the prod DB. Finally, if that causes issues, we can restore the entire DB from a snapshot and rewind the Kafka queues. This would be the worst case scenario as it would cause a few hour interruption where customers wouldn't see recent data, but would not cause data loss.