New Model version not created after changes are committed

**Describe the bug**
Was just walking through SageMaker MLOps Project Example, Its stated in the guide that after new changes are committed, a new version will be creating in model group automatically by the pipeline.

But mine doesn't show, just wondering if I did something wrong. I've already made 2 commits.

Start with the SageMaker MLOps Project Example guide and trace the pipeline steps that should create a new model version after a commit. Verify the two-commit scenario against the model group shown in the issue, then document the cause or the missing setup needed for a new version to appear.

Written by the indexing model from the issue text.