Repo Updates and Content Views Publishing

I am sorry for the silly question but here it goes: after a repo sync/update (packages get changed) is it necessary to publish a new version of the content view using that repo? If that’s the case, can this process be automated? Thank you, and sorry again for the silly question.

yes, you can publish a new version (eg from version 1 to 2) or publish a new incrementa update (eg from 1 to 1.1).
Into Content -> Errata select all the errata -> Apply Errata -> select the servers -> and after you can publish a new incremental update.

For automation: I think you can write a script with the hammer commands, I checked months ago but I don’t had to much time to write something good.

Thank you! I wasn’t able to find a clear answer until now.