fix(ci): pull rebase from main before commit and push in release workflow

[rubencarvalho]

Description

Add git pull --rebase origin main before staging and committing in the release workflow's "Commit and push changes" step.

Motivation and context

If a PR is merged into main between the time the release workflow is triggered and the time the commit/push step runs, the push fails because the local branch is behind the remote. Pulling with rebase before staging ensures the release commit always lands on top of the latest main, avoiding the rejected push.

Related issue(s)

N/A

Screenshots (if appropriate)

N/A

Author's checklist

• I have read the CONTRIBUTING and PULL_REQUESTS documents.
• I have reviewed at the Accessibility Practices for this feature, see: Aria Practices
• I have added automated tests to cover my changes.
• I have included a well-written changeset if my change needs to be published.
• I have included updated documentation if my change required it.

Reviewer's checklist

• Includes a Github Issue with appropriate flag or Jira ticket number without a link
• Includes thoughtfully written changeset if changes suggested include patch, minor, or major features
• Automated tests cover all use cases and follow best practices for writing
• Validated on all supported browsers
• All VRTs are approved before the author can update Golden Hash

Manual review test cases

• Trigger the release workflow while a PR is simultaneously merged to main; verify the workflow completes without a rejected push error.

Device review

• Did it pass in Desktop?
• Did it pass in (emulated) Mobile?
• Did it pass in (emulated) iPad?

Accessibility testing checklist

No interactive UI changes in this PR; CI workflow change only.

• Keyboard — not applicable (no UI changes)
• Screen reader — not applicable (no UI changes)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5eebc73

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[caseyisonit]

wouldnt a rebase rewrite the history? would it be safer to use a merge?

[rubencarvalho]

wouldnt a rebase rewrite the history? would it be safer to use a merge?

@caseyisonit the CI workflow starts "fresh" every run, so there's no history to corrupt, i.e. rebase is safe. A merge would work too, but would leave one merge commit in the release log.

[github-actions]

📚 Branch Preview Links

• Documentation Site (first-gen)
• Storybook (first-gen)
• Storybook (second-gen)

🔍 First Generation Visual Regression Test Results

When a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:

• Spectrum | Light | Medium | LTR
• Spectrum | Dark | Large | RTL
• Express | Light | Medium | LTR
• Express | Dark | Large | RTL
• Spectrum-two | Light | Medium | LTR
• Spectrum-two | Dark | Large | RTL
• High Contrast Mode | Medium | LTR

Deployed to Azure Blob Storage: pr-6338

If the changes are expected, update the current_golden_images_cache hash in the circleci config to accept the new images. Instructions are included in that file.
If the changes are unexpected, you can investigate the cause of the differences and update the code accordingly.