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.

Sign up for GitHub

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

Jump to bottom

Version Packages #475

Merged
merged 1 commit into from
Feb 13, 2024
Merged

Version Packages #475

merged 1 commit into from
Feb 13, 2024

Conversation

ct-changesets[bot]
Copy link
Contributor

@ct-changesets ct-changesets bot commented Feb 6, 2024 •
edited
Loading

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

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Minor Changes

  • #472 f027639 Thanks @jaikamat! - Create standalone prices model and associated draft, support channel key reference preset

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Minor Changes

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Minor Changes

  • #472 f027639 Thanks @jaikamat! - Create standalone prices model and associated draft, support channel key reference preset

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Major Changes

  • #478 71eb4f5 Thanks @jaikamat! - This breaking release excludes __typename from built GraphQL draft models.

    Updating this package will require changes in your codebase. To migrate:

    • Ensure tests that assert on the presence of __typename in draft GraphQL models are updated to no longer expect this field.
    • Update any code that relies on the presence of __typename in draft GraphQL models to align with the new approach.

Patch Changes

@commercetools-test-data/[email protected]

Minor Changes

  • #472 f027639 Thanks @jaikamat! - Create standalone prices model and associated draft, support channel key reference preset

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

Patch Changes

@commercetools-test-data/[email protected]

@commercetools-test-data/[email protected]

@ct-changesets ct-changesets bot requested review from a team as code owners February 6, 2024 11:53
@ct-changesets ct-changesets bot force-pushed the changeset-release/main branch from c40b303 to 86f5903 Compare February 6, 2024 20:44
@ct-changesets ct-changesets bot force-pushed the changeset-release/main branch 3 times, most recently from f3299a0 to daf845d Compare February 13, 2024 19:01
@ct-changesets ct-changesets bot force-pushed the changeset-release/main branch from daf845d to 60f02db Compare February 13, 2024 20:05
@valoriecarli valoriecarli merged commit afc3821 into main Feb 13, 2024
3 checks passed
@valoriecarli valoriecarli deleted the changeset-release/main branch February 13, 2024 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jaikumar-tj jaikumar-tj jaikumar-tj approved these changes

@jaikamat jaikamat jaikamat approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@jaikamat @jaikumar-tj @valoriecarli