Currently, minor schema updates trigger a schema migration batch job that includes a publish step. This publish step auto-publishes all revisions created by the schema migration (i.e. if a collection was public with no revisions pre-migration, it will be migrated in a revision + published).
For major schema updates, we do NOT want to auto-publish. However, the rest of the process will be exactly the same as a minor schema version update. Therefore, we should accept a flag in the schema migration batch job input that allows us to skip the publish step in the case of a major schema update.
Currently, minor schema updates trigger a schema migration batch job that includes a publish step. This publish step auto-publishes all revisions created by the schema migration (i.e. if a collection was public with no revisions pre-migration, it will be migrated in a revision + published).
For major schema updates, we do NOT want to auto-publish. However, the rest of the process will be exactly the same as a minor schema version update. Therefore, we should accept a flag in the schema migration batch job input that allows us to skip the publish step in the case of a major schema update.