How to add new RPMs to a Content View without pushing updates for the existing repositories in Red Hat Satellite 6

Solution Verified - Updated 2020-10-28T09:59:18+00:00 -

Issue

When adding new packages or a new repository to a Content View, a new version has to be published, this inadvertently pushes updates for the existing repositories in the Content View.
Is it possible to maintain the existing repositories at the same version, while adding new packages or repositories to a Content View?

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.