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

Regenerate core for 2025-01 #92

Merged
merged 1 commit into from
Jan 8, 2025

Conversation

austin-denoble
Copy link
Contributor

@austin-denoble austin-denoble commented Jan 8, 2025

Problem

In preparation for the upcoming API version release, we need to regenerate the client code off of the specifications for 2025-01.

Solution

This PR regenerates the client core from main, and merges the updates into the RC branch: 2025-01. This branch is currently synced with main.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • Infrastructure change (CI configs, etc)
  • Non-code change (docs, etc)
  • None of the above: (explain here)

Test Plan

Ran unit and integration tests locally to validate changes. Make sure CI is green before merging into the RC branch.


@austin-denoble austin-denoble requested a review from haruska January 8, 2025 17:43
@austin-denoble austin-denoble merged commit c349bee into 2025-01 Jan 8, 2025
2 checks passed
@austin-denoble austin-denoble deleted the adenoble/update-generated-core-2025-01 branch January 8, 2025 18:59
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