- Notifications
You must be signed in to change notification settings - Fork3.3k
[release/9.0-staging] Don't throw PendingModelChangesWarning when applying a specific migration#35353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
5cbe408 intorelease/9.0-stagingUh oh!
There was an error while loading.Please reload this page.
rickycai-2020 commentedJan 14, 2025
@AndriySvyryd when this change will release since we have a security issue related to this. |
AndriySvyryd commentedJan 14, 2025
@rickycai-2020 9.0.2 - February |
frankgalindo commentedJan 27, 2025
Do you have a more specific date, such as the exact day or even the week? |
AndriySvyryd commentedJan 27, 2025
@frankgalindo We usually align our releases with Patch Tuesday, so it would be Feb 11. But there is always a possibility of something going wrong and delaying the release. |
Fixes#35342
Port of#35343
Improvement of#35221
Description
In 9.0 we added a runtime warning that would throw by default when updating the database if there are any changes detected in the model that aren't reflected in the latest migration.
However, when applying a specific migration this warning is not relevant and could be confusing.
Customer impact
The workaround is to ignore the warning using options.
How found
Customer report on 9, part of a large stream of feedback around this warning.
Regression
Yes, from 8.
Testing
Test added
Risk
Low.