Skip to content

Conversation

@lgriffee
Copy link
Contributor

@lgriffee lgriffee commented Oct 4, 2023

WHY are these changes introduced?

In order to run the v12-react-avatar-component migration as part of our beta release it needs to be merged and released on main instead of the next branch.

WHAT is this pull request doing?

Ports over v12-react-avatar-component migration from [Avatar] Remove customer prop and experiemntal values #10283 to main branch

@lgriffee lgriffee requested a review from a team as a code owner October 4, 2023 17:13
@lgriffee lgriffee self-assigned this Oct 4, 2023
@lgriffee lgriffee requested a review from a team as a code owner October 4, 2023 17:13
lgriffee and others added 3 commits October 4, 2023 11:17
Co-authored-by: Lo Kim <lo.kim@shopify.com>
Co-Authored-By: Lo Kim <26749317+laurkim@users.noreply.github.com>
Copy link
Member

@sam-b-rose sam-b-rose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

@lgriffee lgriffee merged commit 471c3d5 into main Oct 4, 2023
@lgriffee lgriffee deleted the avatar-migration branch October 4, 2023 17:39
lgriffee pushed a commit that referenced this pull request Oct 4, 2023
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @shopify/polaris-migrator@0.24.0

### Minor Changes

- [#10874](#10874)
[`471c3d5af`](471c3d5)
Thanks [@lgriffee](https://github.com/lgriffee)! - Ported
`v12-react-avatar-component` migration from [Avatar] Remove customer
prop and experimental values
[#10283](#10283) to main branch

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@lgriffee lgriffee restored the avatar-migration branch October 4, 2023 21:30
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
In order to run the `v12-react-avatar-component` migration as part of
our beta release it needs to be merged and released on `main` instead of
the `next` branch.

Ports over `v12-react-avatar-component` migration from [[Avatar] Remove
customer prop and experiemntal values

---------

Co-authored-by: Lo Kim <lo.kim@shopify.com>
Co-authored-by: Lo Kim <26749317+laurkim@users.noreply.github.com>
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @shopify/polaris-migrator@0.24.0

### Minor Changes

- [#10874](#10874)
[`471c3d5af`](471c3d5)
Thanks [@lgriffee](https://github.com/lgriffee)! - Ported
`v12-react-avatar-component` migration from [Avatar] Remove customer
prop and experimental values
[#10283](#10283) to main branch

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
In order to run the `v12-react-avatar-component` migration as part of
our beta release it needs to be merged and released on `main` instead of
the `next` branch.

Ports over `v12-react-avatar-component` migration from [[Avatar] Remove
customer prop and experiemntal values

---------

Co-authored-by: Lo Kim <lo.kim@shopify.com>
Co-authored-by: Lo Kim <26749317+laurkim@users.noreply.github.com>
mrcthms pushed a commit that referenced this pull request Oct 12, 2023
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @shopify/polaris-migrator@0.24.0

### Minor Changes

- [#10874](#10874)
[`471c3d5af`](471c3d5)
Thanks [@lgriffee](https://github.com/lgriffee)! - Ported
`v12-react-avatar-component` migration from [Avatar] Remove customer
prop and experimental values
[#10283](#10283) to main branch

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
AnnaCheba pushed a commit to AnnaCheba/polaris that referenced this pull request Apr 22, 2024
### WHY are these changes introduced?

In order to run the `v12-react-avatar-component` migration as part of
our beta release it needs to be merged and released on `main` instead of
the `next` branch.

### WHAT is this pull request doing?
Ports over `v12-react-avatar-component` migration from [[Avatar] Remove
customer prop and experiemntal values
Shopify#10283](Shopify#10283) to main branch

---------

Co-authored-by: Lo Kim <lo.kim@shopify.com>
Co-authored-by: Lo Kim <26749317+laurkim@users.noreply.github.com>
ascherkus pushed a commit to ascherkus/polaris that referenced this pull request Feb 19, 2025
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @shopify/polaris-migrator@0.24.0

### Minor Changes

- [Shopify#10874](Shopify#10874)
[`471c3d5af`](Shopify@f5fe112)
Thanks [@lgriffee](https://github.com/lgriffee)! - Ported
`v12-react-avatar-component` migration from [Avatar] Remove customer
prop and experimental values
[Shopify#10283](Shopify#10283) to main branch

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants