Add features requiring finalization to v25.1 major release notes

[mikeCRL]

DOC-12267

[github-actions]

Files changed:

• src/current/_includes/releases/v25.1/upgrade-finalization.md:
  • releases/v25.1.md

[netlify]

✅ Deploy Preview for cockroachdb-api-docs canceled.

Name	Link
🔨 Latest commit	22ef22d
🔍 Latest deploy log	https://app.netlify.com/sites/cockroachdb-api-docs/deploys/67b617796447ad00081841d4

[netlify]

✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name	Link
🔨 Latest commit	22ef22d
🔍 Latest deploy log	https://app.netlify.com/sites/cockroachdb-interactivetutorials-docs/deploys/67b617792e0419000737b4bc

[netlify]

✅ Netlify Preview

Name	Link
🔨 Latest commit	22ef22d
🔍 Latest deploy log	https://app.netlify.com/sites/cockroachdb-docs/deploys/67b617799bc9f100085a6223
😎 Deploy Preview	https://deploy-preview-19379--cockroachdb-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dt]

@spilchen should ALTER COLUMN TYPE be in this list too?
@DrewKimball should DO statements be here?
@fqazi anything we should mention about memo staleness or waiting for initial versions of descs here?

[fqazi]

@dt Those are internal to the product, and shouldn't have any visible external changes.

[spilchen]

@spilchen should ALTER COLUMN TYPE be in this list too?

Yes, I think it should. ALTER COLUMN TYPE existed before version 25.1, but it was in experimental mode and not ready for GA. Once 25.1 is finalized, you can use the new logic in the declarative schema changer to support this operation.

[spilchen]

I think ALTER COLUMN TYPE should be included in the list of features that require finalization. Will that be covered in a separate PR?

[mikeCRL]

@spilchen Yes, @rmloveland will be adding this soon. I'd merged this before seeing your comment, then asked Rich to cover it once I noticed. Thanks.

[DrewKimball]

@DrewKimball should DO statements be here?

Regular DO statements aren't persisted, so don't need a version check. A DO statement within a routine does require the finalized version, though.