Status report still shows "The Active field needs to be updated" after running updates

There should be no need for entup because each module's updates should perform the needed changes.

However, I can confirm that locally I am also seeing that message, even though all updates have been run.
We have a bug.

I Have the same problerm?

Drupal 8.6.15
Same Problem :-(
Thanks for help.

EntityPublishedTrait defines the status field as "translatable", which wasn't the case with the manual base field definition we had before.
I believe it shouldn't be translatable since none of the other fields are.

After running the update, the warning is gone.

#5 solved the problem for me.

#5 solved the problem for me too.

sorry, not working for me :(

@benjarlett: did you apply the patch and ran the updates?

I can confirm this works

#5 solved the problem for me too.

#5 rocks

Committed #5, thanks jsacksick!

I added the patch to my composer.json, did an update with composer which applied the patch, run update.php and the error is gone.

Should I now remove the patch reference from composer.json before the next composer update?

Thanks for you comments!

#5 worked but had to apply the patch with:

patch -p1 < some_patchfile_.patch

rather than:

git apply patch some_patchfile.patch

usually the git-way worked but in this case, no error, no patching at all :/

#5 patch resolved the issue

my process:
downloaded patch file into the profile module directory
profile-fix-status-field-3060368-5.patch

terminal into profile module directory
terminal: $ patch -p 1 < profile-fix-status-field-3060368-5.patch

terminal into drupal install directory
drush updb

happy dance

Hello,

I have the same problem :
"Profile
The Active field needs to be updated."

I have done all the updates but the error message remains.
Should I apply the patch : "profile-fix-status-field-3060368-5.patch" ?
And How ? (I am not using composer an drush).

Thank you.

@quapou https://www.drupal.org/node/620014

Confirming that #5 patch works for me.

I confirm that after applying the patch #5, the update runs normally and there is no more warning message.
To reply to #mlecha, it is then possible to remove the patch and redo a composer update, the database having been updated, there is no more warning.
Thanks

Update to rc6, no need for a patch anymore.

Update to rc6, no need for a patch anymore.