Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #596

Merged
merged 1 commit into from
Nov 18, 2021
Merged

Version Packages #596

merged 1 commit into from
Nov 18, 2021

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 29, 2021

This PR was opened by the Changesets release 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

@aws-amplify/[email protected]

Major Changes

  • #745 3ead9c629 Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & Vue

    The Authenticator has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.

    See: RFC: Authenticator@next

    Goals

    • Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.

      	Run `amplify pull` with the latest CLI whenever your backend changes, and the Authenticator automatically reflects the correct login mechanism, social providers, & more.
      
    • Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.

    • Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.

      	[Authenticator behavior](https:/aws-amplify/amplify-ui/tree/main/packages/e2e/features/ui/components/authenticator) is tested as [E2E tests](https:/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#e2e-testing) on every PR.
      
    • Interoperable – Work with password managers, autofill, existing styles, & other common features.

    • Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.

      	Customers have access to the same functionality that the `Authenticator` uses internally to even build a 100% custom Authenticator, without sacrificing any of the logic.
      
    • Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.

      	Check out our [environments](https:/aws-amplify/amplify-ui/tree/main/environments) and [examples](https:/aws-amplify/amplify-ui/tree/main/examples) for more.
      

    Learn more by visiting the Authenticator Documentation.

Minor Changes

  • #626 f84e9949b Thanks @ericclemmons! - ## Zero Configuration

    As of @aws-amplify/[email protected], aws-exports.js includes your backend configuration for the Authenticator to automatically infer loginMechanisms and socialProviders.

    Before (React)

    export default withAuthenticator(App, {
      loginMechanisms: ['email'],
      socialProviders: ['amazon', 'apple', 'facebook', 'google']
    })

    After (React)

    export default withAuthenticator(App)

    Sign in with Apple

    The Authenticator supports apple as one of many socialProviders. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/

  • #610 1fc955c4e Thanks @wlee221! - Add sign-up-form-field slot and component

  • #627 bd3e09a09 Thanks @wlee221! - This implements AuthenticatorService that can be used internally and externally to access common Authenticator context and helpers.

    Usage:

    app.component.ts

    export class AppComponent {
      constructor(public authenticator: AuthenticatorService) {}
    }

    app.component.html

    <!-- example of "reset password" button -->
    <button (click)="authenticator.toResetPassword()">Reset password</button>
    
    <!-- example of "sign up" submit button -->
    <button (click)="authenticator.submitForm()">Sign Up</button>
    
    <!-- disabling the submit button if submission is in progress -->
    <button
      (click)="authenticator.submitForm()"
      [disabled]="authenticator.isPending"
    >
      Sign Up
    </button>
  • #628 ef1e0f000 Thanks @wlee221! - Add and expose amplify-checkbox

  • #628 ef1e0f000 Thanks @wlee221! - Add services prop and custom-sign-up example. See documentation for usage notes.

Patch Changes

@aws-amplify/[email protected]

Major Changes

  • #747 81169c66e Thanks @wlee221! - New primitive components and theming API

    Amplify UI is building primitive components like badges, cards, alerts, etc. These primitive components will first be available on React with the goal of adding support for more frameworks in the future. We hope these primitives will empower developers to build applications faster. We plan on building out more connected components like the Authenticator and we need primitive components like buttons and inputs to be shared across them. Exposing these primitive components allows developers to create and theme applications end-to-end using the same components everywhere.

    See: RFC: Amplify UI Primitive Components

    Goals

    Flexible – Primitives can be integrated into as many applications as possible.
    Customizable – Primitives can be composed and styled using a theme, CSS, a CSS-in-JS framework, or un-styled.
    Accessible – Primitives follow WCAG and WAI-ARIA guidelines to make building accessible applications easy.
    Basic

    Implementation

    • Added 37 new React primitive components such as Button, TextField, Alert that are the building blocks to create consistency across connected components.
    • Added Theming API to allow global and component-override theming. Theme structure uses design tokens including borderWidth, colors, fonts, fontSizes, fontWeights, LineHeights, opacities and breakpoints.
    • Documentation: https://ui.docs.amplify.aws/components
  • #745 3ead9c629 Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & Vue

    The Authenticator has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.

    See: RFC: Authenticator@next

    Goals

    • Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.

      	Run `amplify pull` with the latest CLI whenever your backend changes, and the Authenticator automatically reflects the correct login mechanism, social providers, & more.
      
    • Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.

    • Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.

      	[Authenticator behavior](https:/aws-amplify/amplify-ui/tree/main/packages/e2e/features/ui/components/authenticator) is tested as [E2E tests](https:/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#e2e-testing) on every PR.
      
    • Interoperable – Work with password managers, autofill, existing styles, & other common features.

    • Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.

      	Customers have access to the same functionality that the `Authenticator` uses internally to even build a 100% custom Authenticator, without sacrificing any of the logic.
      
    • Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.

      	Check out our [environments](https:/aws-amplify/amplify-ui/tree/main/environments) and [examples](https:/aws-amplify/amplify-ui/tree/main/examples) for more.
      

    Learn more by visiting the Authenticator Documentation.

Minor Changes

  • #626 f84e9949b Thanks @ericclemmons! - ## Zero Configuration

    As of @aws-amplify/[email protected], aws-exports.js includes your backend configuration for the Authenticator to automatically infer loginMechanisms and socialProviders.

    Before (React)

    export default withAuthenticator(App, {
      loginMechanisms: ['email'],
      socialProviders: ['amazon', 'apple', 'facebook', 'google']
    })

    After (React)

    export default withAuthenticator(App)

    Sign in with Apple

    The Authenticator supports apple as one of many socialProviders. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/

  • #650 e76c5ac17 Thanks @ericclemmons! - ## signUpAttributes

    The Sign Up form will include most of https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-attributes.html by default with zero-config.

    Any verification mechanisms (e.g. email, phone_number) will always be required.

  • #698 5482edcbb Thanks @reesscot! - Add forwardRef support to Button & View

  • #716 e155ef0be Thanks @reesscot! - Remove AmplifyProvider custom components feature

  • #717 edea9ffaa Thanks @dbanksdesign! - Adding card variations

    <Card>
      Default card
    </Card>
    
    <Card variation="outlined">
      Outlined card
    </Card>
    
    <Card variation="elevated">
      Elevated card
    </Card>
  • #653 70552a4cc Thanks @reesscot! - Icon size now matches parent font-size. Allows customers to more easily use icons alongsize Headings, Buttons, etc.

    Example:

    <Button gap="0.1rem" size="small">
        <IconSave /> Save
    </Button>
    
  • #582 3143deff1 Thanks @ericclemmons! - AmplifyProvider accepts a partial list of primitives as components:

    const App = () => {
      const {
        components: { Heading },
      } = useAmplify();
    
      return <Heading>Howdy</Heading>;
    };
    
    <AmplifyProvider
      components={{
        Heading({ children }) {
          return <h1>{children}</h1>;
        },
      }}
    >
      <App />
    </AmplifyProvider>;

Patch Changes

  • #737 8f0301f0b Thanks @reesscot! - ForwardRef support - CountryCode, SelectField, and SliderField

  • #552 bba3242af Thanks @ericclemmons! - @aws-amplify/ui-react supports validation & re-use & customization of Authenticator.SignUp.FormFields via components & services:

    <Authenticator
      components={{
        SignUp: {
          FormFields() {
            const { validationErrors } = useAuthenticator();
            return (
              <>
                <TextField
                  label="Preferred Username"
                  labelHidden={true}
                  name="preferred_username"
                  placeholder="Preferred Username"
                />
                <Authenticator.SignUp.FormFields />
                <CheckboxField
                  errorMessage={validationErrors.acknowledgement}
                  hasError={!!validationErrors.acknowledgement}
                  label="I agree with the Terms & Conditions"
                  name="acknowledgement"
                  value="yes"
                />
              </>
            );
          },
        },
      }}
      services={{
        async validateCustomSignUp(formData) {
          if (!formData.acknowledgement) {
            return {
              acknowledgement: 'You must agree to the Terms & Conditions',
            };
          }
        },
      }}
    />
  • #617 77fa42da5 Thanks @hvergara! - Fix primitives catalog generator

  • #720 84a86b4ef Thanks @reesscot! - ForwardRef support - Flex and Grid

  • #761 a82e422f3 Thanks @reesscot! - ForwardRef support for TextField

  • #709 3cc1c15d7 Thanks @dbanksdesign! - Building icons from Figma source now.

  • #618 943d4b661 Thanks @hvergara! - Make style prop types more flexible

  • #636 5e31719f1 Thanks @hvergara! - useStorageURL React hook

  • #725 8f4d8129c Thanks @reesscot! - ForwardRef support - misc view-based primitives

  • #601 f6d144dc3 Thanks @hvergara! - Add useAuth React hook

  • #731 c5ae2f44a Thanks @reesscot! - ForwardRef support - textarea, checkbox, radio

  • #568 36d256b02 Thanks @slaymance! - Adds React Table primitive

  • #727 2b2ae8469 Thanks @dbanksdesign! - * Divider component has more theming options for the border style, color, and width.

    • Fixing vertical divider
    • Improving Divider docs
  • #721 e90085e1d Thanks @reesscot! - Forward ref inputs

  • #695 d5009572c Thanks @ericclemmons! - ## Header & Footer Slots

    • Add Header slot above the Authenticator
    • Add Footer slot below the Authenticator
    • Add Sign In Header slot above the Sign In form
    • Add Sign In Footer slot below the Sign In form
    • Add Sign Up Header slot above the Sign Up form
    • Add Sign Up Footer slot below the Sign Up form
  • #719 df2bcb749 Thanks @reesscot! - ForwardRef support - base primitives

  • #612 beb9b49b5 Thanks @reesscot! - Menu primitive

    New primitive which enables customers to create aaccessible, interactive menu for selecting actions within an application.
    Dropdown menu is collision-aware and will automatically change location based on available space.

    import { Divider, Menu, MenuItem } from '@aws-amplify/ui-react';
    
    export const BasicExample = () => {
      return (
        <Menu>
          <MenuItem onClick={() => alert('Download')}>Download</MenuItem>
          <MenuItem onClick={() => alert('Create a Copy')}>Create a Copy</MenuItem>
          <MenuItem onClick={() => alert('Mark as Draft')}>Mark as Draft</MenuItem>
          <Divider />
          <MenuItem isDisabled onClick={() => alert('Delete')}>
            Delete
          </MenuItem>
          <MenuItem onClick={() => alert('Attend a workshop')}>
            Attend a workshop
          </MenuItem>
        </Menu>
      );
    };
  • #638 d71e65609 Thanks @ericclemmons! - Fix getOverrideProps to return all, not just 2

  • #634 5257a3109 Thanks @dbanksdesign! - Adding support for token style props in React components and moving createTheme inside the AmplifyProvider so users don't have to call it directly in React.

    const theme: Theme = {
      name: 'my-theme',
      tokens: {
        //...
      }
    }
    
    const App = () => {
      return (
        <AmplifyProvider theme={theme}>
    
        </AmplifyProvider>
      )
    }

    Then using theme tokens in a style prop:

    import { useTheme, Text } from '@aws-amplify/ui-react';
    
    const MyComponent = () => {
      const { tokens } = useTheme();
      return (
        <Text color={tokens.colors.font.error}>Error!</Text>
      )
    }

    The ui-react package is now exporting the Theme type to make it easier to define a theme object outside of the createTheme method.

  • #748 ca04c8dbc Thanks @reesscot! - Remove internal fieldgroup export

  • Updated dependencies [bba3242af, f84e9949b, e76c5ac17, 81169c66e, 3cc1c15d7, 2b2ae8469, b46597cef, edea9ffaa, bd3e09a09, 70552a4cc, beb9b49b5, 5257a3109, 3ead9c629]:

@aws-amplify/[email protected]

Major Changes

  • #747 81169c66e Thanks @wlee221! - New primitive components and theming API

    Amplify UI is building primitive components like badges, cards, alerts, etc. These primitive components will first be available on React with the goal of adding support for more frameworks in the future. We hope these primitives will empower developers to build applications faster. We plan on building out more connected components like the Authenticator and we need primitive components like buttons and inputs to be shared across them. Exposing these primitive components allows developers to create and theme applications end-to-end using the same components everywhere.

    See: RFC: Amplify UI Primitive Components

    Goals

    Flexible – Primitives can be integrated into as many applications as possible.
    Customizable – Primitives can be composed and styled using a theme, CSS, a CSS-in-JS framework, or un-styled.
    Accessible – Primitives follow WCAG and WAI-ARIA guidelines to make building accessible applications easy.
    Basic

    Implementation

    • Added 37 new React primitive components such as Button, TextField, Alert that are the building blocks to create consistency across connected components.
    • Added Theming API to allow global and component-override theming. Theme structure uses design tokens including borderWidth, colors, fonts, fontSizes, fontWeights, LineHeights, opacities and breakpoints.
    • Documentation: https://ui.docs.amplify.aws/components
  • #745 3ead9c629 Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & Vue

    The Authenticator has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.

    See: RFC: Authenticator@next

    Goals

    • Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.

      	Run `amplify pull` with the latest CLI whenever your backend changes, and the Authenticator automatically reflects the correct login mechanism, social providers, & more.
      
    • Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.

    • Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.

      	[Authenticator behavior](https:/aws-amplify/amplify-ui/tree/main/packages/e2e/features/ui/components/authenticator) is tested as [E2E tests](https:/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#e2e-testing) on every PR.
      
    • Interoperable – Work with password managers, autofill, existing styles, & other common features.

    • Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.

      	Customers have access to the same functionality that the `Authenticator` uses internally to even build a 100% custom Authenticator, without sacrificing any of the logic.
      
    • Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.

      	Check out our [environments](https:/aws-amplify/amplify-ui/tree/main/environments) and [examples](https:/aws-amplify/amplify-ui/tree/main/examples) for more.
      

    Learn more by visiting the Authenticator Documentation.

Minor Changes

  • #626 f84e9949b Thanks @ericclemmons! - ## Zero Configuration

    As of @aws-amplify/[email protected], aws-exports.js includes your backend configuration for the Authenticator to automatically infer loginMechanisms and socialProviders.

    Before (React)

    export default withAuthenticator(App, {
      loginMechanisms: ['email'],
      socialProviders: ['amazon', 'apple', 'facebook', 'google']
    })

    After (React)

    export default withAuthenticator(App)

    Sign in with Apple

    The Authenticator supports apple as one of many socialProviders. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/

  • #650 e76c5ac17 Thanks @ericclemmons! - ## signUpAttributes

    The Sign Up form will include most of https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-attributes.html by default with zero-config.

    Any verification mechanisms (e.g. email, phone_number) will always be required.

  • #717 edea9ffaa Thanks @dbanksdesign! - Adding card variations

    <Card>
      Default card
    </Card>
    
    <Card variation="outlined">
      Outlined card
    </Card>
    
    <Card variation="elevated">
      Elevated card
    </Card>
  • #627 bd3e09a09 Thanks @wlee221! - This implements AuthenticatorService that can be used internally and externally to access common Authenticator context and helpers.

    Usage:

    app.component.ts

    export class AppComponent {
      constructor(public authenticator: AuthenticatorService) {}
    }

    app.component.html

    <!-- example of "reset password" button -->
    <button (click)="authenticator.toResetPassword()">Reset password</button>
    
    <!-- example of "sign up" submit button -->
    <button (click)="authenticator.submitForm()">Sign Up</button>
    
    <!-- disabling the submit button if submission is in progress -->
    <button
      (click)="authenticator.submitForm()"
      [disabled]="authenticator.isPending"
    >
      Sign Up
    </button>
  • #653 70552a4cc Thanks @reesscot! - Icon size now matches parent font-size. Allows customers to more easily use icons alongsize Headings, Buttons, etc.

    Example:

    <Button gap="0.1rem" size="small">
        <IconSave /> Save
    </Button>
    

Patch Changes

  • #552 bba3242af Thanks @ericclemmons! - @aws-amplify/ui-react supports validation & re-use & customization of Authenticator.SignUp.FormFields via components & services:

    <Authenticator
      components={{
        SignUp: {
          FormFields() {
            const { validationErrors } = useAuthenticator();
            return (
              <>
                <TextField
                  label="Preferred Username"
                  labelHidden={true}
                  name="preferred_username"
                  placeholder="Preferred Username"
                />
                <Authenticator.SignUp.FormFields />
                <CheckboxField
                  errorMessage={validationErrors.acknowledgement}
                  hasError={!!validationErrors.acknowledgement}
                  label="I agree with the Terms & Conditions"
                  name="acknowledgement"
                  value="yes"
                />
              </>
            );
          },
        },
      }}
      services={{
        async validateCustomSignUp(formData) {
          if (!formData.acknowledgement) {
            return {
              acknowledgement: 'You must agree to the Terms & Conditions',
            };
          }
        },
      }}
    />
  • #709 3cc1c15d7 Thanks @dbanksdesign! - Building icons from Figma source now.

  • #727 2b2ae8469 Thanks @dbanksdesign! - * Divider component has more theming options for the border style, color, and width.

    • Fixing vertical divider
    • Improving Divider docs
  • #615 b46597cef Thanks @reesscot! - Apply box-sizing: border-box styling to all Amplify theme children

  • #612 beb9b49b5 Thanks @reesscot! - Menu primitive

    New primitive which enables customers to create aaccessible, interactive menu for selecting actions within an application.
    Dropdown menu is collision-aware and will automatically change location based on available space.

    import { Divider, Menu, MenuItem } from '@aws-amplify/ui-react';
    
    export const BasicExample = () => {
      return (
        <Menu>
          <MenuItem onClick={() => alert('Download')}>Download</MenuItem>
          <MenuItem onClick={() => alert('Create a Copy')}>Create a Copy</MenuItem>
          <MenuItem onClick={() => alert('Mark as Draft')}>Mark as Draft</MenuItem>
          <Divider />
          <MenuItem isDisabled onClick={() => alert('Delete')}>
            Delete
          </MenuItem>
          <MenuItem onClick={() => alert('Attend a workshop')}>
            Attend a workshop
          </MenuItem>
        </Menu>
      );
    };
  • #634 5257a3109 Thanks @dbanksdesign! - Adding support for token style props in React components and moving createTheme inside the AmplifyProvider so users don't have to call it directly in React.

    const theme: Theme = {
      name: 'my-theme',
      tokens: {
        //...
      }
    }
    
    const App = () => {
      return (
        <AmplifyProvider theme={theme}>
    
        </AmplifyProvider>
      )
    }

    Then using theme tokens in a style prop:

    import { useTheme, Text } from '@aws-amplify/ui-react';
    
    const MyComponent = () => {
      const { tokens } = useTheme();
      return (
        <Text color={tokens.colors.font.error}>Error!</Text>
      )
    }

    The ui-react package is now exporting the Theme type to make it easier to define a theme object outside of the createTheme method.

@aws-amplify/[email protected]

Major Changes

  • #745 3ead9c629 Thanks @wlee221! - Zero-Configuration Authenticator for Angular, React, & Vue

    The Authenticator has been updated based on customer feedback & real-world use-cases to deliver an improved out-of-the-box experience & greater customization.

    See: RFC: Authenticator@next

    Goals

    • Zero-config – The Authenticator automatically infers Amplify CLI & Admin UI settings to work out-of-the-box.

      	Run `amplify pull` with the latest CLI whenever your backend changes, and the Authenticator automatically reflects the correct login mechanism, social providers, & more.
      
    • Native – The Authenticator is implemented in its respective framework (e.g. Angular, React, Vue) for consistency & familiarity.

    • Stable – Existing & upcoming Authenticator behavior is captured & tested to reduce & prevent regressions.

      	[Authenticator behavior](https:/aws-amplify/amplify-ui/tree/main/packages/e2e/features/ui/components/authenticator) is tested as [E2E tests](https:/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#e2e-testing) on every PR.
      
    • Interoperable – Work with password managers, autofill, existing styles, & other common features.

    • Customizable – More ways to customize the UI & behavior without losing the benefits of the Authenticator.

      	Customers have access to the same functionality that the `Authenticator` uses internally to even build a 100% custom Authenticator, without sacrificing any of the logic.
      
    • Reproducible – Authentication is complex. The Authenticator is is developed & tested against a myriad of Amplify backends, example apps, and specifications.

      	Check out our [environments](https:/aws-amplify/amplify-ui/tree/main/environments) and [examples](https:/aws-amplify/amplify-ui/tree/main/examples) for more.
      

    Learn more by visiting the Authenticator Documentation.

Minor Changes

  • #626 f84e9949b Thanks @ericclemmons! - ## Zero Configuration

    As of @aws-amplify/[email protected], aws-exports.js includes your backend configuration for the Authenticator to automatically infer loginMechanisms and socialProviders.

    Before (React)

    export default withAuthenticator(App, {
      loginMechanisms: ['email'],
      socialProviders: ['amazon', 'apple', 'facebook', 'google']
    })

    After (React)

    export default withAuthenticator(App)

    Sign in with Apple

    The Authenticator supports apple as one of many socialProviders. See: https://docs.amplify.aws/lib/auth/social/q/platform/js/

  • #627 bd3e09a09 Thanks @wlee221! - This implements AuthenticatorService that can be used internally and externally to access common Authenticator context and helpers.

    Usage:

    app.component.ts

    export class AppComponent {
      constructor(public authenticator: AuthenticatorService) {}
    }

    app.component.html

    <!-- example of "reset password" button -->
    <button (click)="authenticator.toResetPassword()">Reset password</button>
    
    <!-- example of "sign up" submit button -->
    <button (click)="authenticator.submitForm()">Sign Up</button>
    
    <!-- disabling the submit button if submission is in progress -->
    <button
      (click)="authenticator.submitForm()"
      [disabled]="authenticator.isPending"
    >
      Sign Up
    </button>

Patch Changes

@wlee221
Copy link
Contributor

wlee221 commented Oct 29, 2021

Please don't merge this until we're ready to release to latest.

@github-actions github-actions bot force-pushed the changeset-release/main branch 14 times, most recently from 6d852bc to a6b572a Compare November 4, 2021 16:28
@github-actions github-actions bot force-pushed the changeset-release/main branch 9 times, most recently from 83e407f to 2ae32a3 Compare November 8, 2021 18:43
Copy link
Contributor

@ericclemmons ericclemmons left a comment

Choose a reason for hiding this comment

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

We'll need to review & editorialize changelogs one last time before we merge this 👀

@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from 231a776 to 166c821 Compare November 9, 2021 19:25
@github-actions github-actions bot force-pushed the changeset-release/main branch 8 times, most recently from 8e65845 to 1002405 Compare November 18, 2021 18:36
@github-actions github-actions bot force-pushed the changeset-release/main branch 3 times, most recently from ec3209c to 6443246 Compare November 18, 2021 20:40
@wlee221 wlee221 temporarily deployed to ci November 18, 2021 21:35 Inactive
@wlee221 wlee221 temporarily deployed to ci November 18, 2021 21:35 Inactive
@wlee221 wlee221 temporarily deployed to ci November 18, 2021 21:35 Inactive
@wlee221 wlee221 temporarily deployed to ci November 18, 2021 21:49 Inactive
@wlee221 wlee221 merged commit d45ab37 into main Nov 18, 2021
@wlee221 wlee221 deleted the changeset-release/main branch November 18, 2021 21:58
thaddmt added a commit that referenced this pull request Apr 7, 2023
* fix(android/firefox): adjust streaming video size for testing (#593)

Co-authored-by: Heather Buchel <[email protected]>

* fix: iPad video constraints and device detection  (#594)

* Test for mobile device

* fix ipad detection, move to utils

Co-authored-by: Heather Buchel <[email protected]>

* Ipad safari (#595)

fix: update detection for ipad so it passes the isIOS check

* fix: update freshness color canvas to 100% width and height (#596)

* fix: livenessIconWithPopver to original

Co-authored-by: Heather Buchel <[email protected]>
Co-authored-by: Heather Buchel <[email protected]>
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.

2 participants