Skip to content

Conversation

@joshua-spacetime
Copy link
Collaborator

@joshua-spacetime joshua-spacetime commented Aug 18, 2025

Description of Changes

Disables automigrations for column type changes

API and ABI breaking changes

None

Expected complexity level and risk

0

Testing

  • Updated smoketests

@joshua-spacetime joshua-spacetime marked this pull request as ready for review August 20, 2025 18:43
bfops added a commit that referenced this pull request Aug 20, 2025
@joshua-spacetime joshua-spacetime added this pull request to the merge queue Aug 21, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 21, 2025
@joshua-spacetime joshua-spacetime added this pull request to the merge queue Aug 21, 2025
Merged via the queue into master with commit be1bd22 Aug 21, 2025
25 of 28 checks passed
@joshua-spacetime joshua-spacetime deleted the joshua/disable-col-type-changes branch August 21, 2025 19:30
Centril added a commit that referenced this pull request Aug 25, 2025
github-merge-queue bot pushed a commit that referenced this pull request Aug 26, 2025
# Description of Changes

First commit reverts disabling adding enum variants
(#3178).
Second commit makes replay recognize inserts / deletes to `st_column`
and triggers a refresh of the in-memory table that was referenced in the
`st_column` change.

# API and ABI breaking changes

None

# Expected complexity level and risk

3, small code bug "deep".

# Testing

I've confirmed manually that a module that couldn't be restarted before
this PR can now be restarted.
We should probably follow up this PR with a smoketest.
jdetter pushed a commit that referenced this pull request Aug 26, 2025
gefjon pushed a commit that referenced this pull request Aug 27, 2025
# Description of Changes

First commit reverts disabling adding enum variants
(#3178).
Second commit makes replay recognize inserts / deletes to `st_column`
and triggers a refresh of the in-memory table that was referenced in the
`st_column` change.

# API and ABI breaking changes

None

# Expected complexity level and risk

3, small code bug "deep".

# Testing

I've confirmed manually that a module that couldn't be restarted before
this PR can now be restarted.
We should probably follow up this PR with a smoketest.
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