Skip to content

Conversation

@rohanshah18
Copy link
Contributor

@rohanshah18 rohanshah18 commented Nov 12, 2025

Problem

Update core based on 2025-10 specs

Solution

Generated and updated the core based on the 2025-10 OAS and protos. Note that the code had already been generated from the 2025-10 specs, but some fixes were made to the OAS, so I had to regenerate it.

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

No new functionalities are added in this pr so existing integration tests should pass.

@rohanshah18 rohanshah18 marked this pull request as ready for review November 12, 2025 17:58
@rohanshah18 rohanshah18 changed the base branch from rshah/release-candidate/2025-10 to main November 12, 2025 17:59
@rohanshah18 rohanshah18 changed the base branch from main to update-integ-examples November 12, 2025 17:59
@rohanshah18 rohanshah18 changed the base branch from update-integ-examples to rshah/release-candidate/2025-10 November 12, 2025 18:00
@rohanshah18 rohanshah18 changed the title update oas based code Generate core based on oas and protos Nov 12, 2025
@rohanshah18 rohanshah18 merged commit 59b4ef6 into rshah/release-candidate/2025-10 Nov 12, 2025
9 checks passed
@rohanshah18 rohanshah18 deleted the rshah/update-code branch November 12, 2025 19:13
rohanshah18 added a commit that referenced this pull request Nov 12, 2025
## Problem

Update core based on 2025-10 specs

## Solution

Generated and updated the core based on the 2025-10 OAS and protos. Note
that the code had already been generated from the 2025-10 specs, but
some fixes were made to the OAS, so I had to regenerate it.

## Type of Change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] 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

No new functionalities are added in this pr so existing integration
tests should pass.
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