Skip to content

Release 0.137.13#3275

Merged
odlbot merged 12 commits intoreleasefrom
release-candidate
Feb 5, 2026
Merged

Release 0.137.13#3275
odlbot merged 12 commits intoreleasefrom
release-candidate

Conversation

@odlbot
Copy link
Contributor

@odlbot odlbot commented Feb 5, 2026

Nathan Levesque

James Kachel

renovate[bot]

renovate bot and others added 12 commits February 4, 2026 10:44
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

OpenAPI Changes

Show/hide ## Changes for v0.yaml:
## Changes for v0.yaml:
3 changes: 0 error, 1 warning, 2 info
warning	[response-property-enum-value-added] at head/openapi/specs/v0.yaml	
	in API POST /api/v0/b2b/enroll/{readable_id}/
		added the new 'b2b-error-not-enrollable' enum value to the 'result/allOf[#/components/schemas/ResultEnum]/' response property for the response status '200'
		Adding new enum values to response could be unexpected for clients, use x-extensible-enum instead.

info	[endpoint-added] at head/openapi/specs/v0.yaml	
	in API GET /api/v3/program_enrollments/
		endpoint added

info	[endpoint-added] at head/openapi/specs/v0.yaml	
	in API GET /api/v3/program_enrollments/{program_id}/
		endpoint added



## Changes for v1.yaml:
3 changes: 0 error, 1 warning, 2 info
warning	[response-property-enum-value-added] at head/openapi/specs/v1.yaml	
	in API POST /api/v0/b2b/enroll/{readable_id}/
		added the new 'b2b-error-not-enrollable' enum value to the 'result/allOf[#/components/schemas/ResultEnum]/' response property for the response status '200'
		Adding new enum values to response could be unexpected for clients, use x-extensible-enum instead.

info	[endpoint-added] at head/openapi/specs/v1.yaml	
	in API GET /api/v3/program_enrollments/
		endpoint added

info	[endpoint-added] at head/openapi/specs/v1.yaml	
	in API GET /api/v3/program_enrollments/{program_id}/
		endpoint added



## Changes for v2.yaml:
3 changes: 0 error, 1 warning, 2 info
warning	[response-property-enum-value-added] at head/openapi/specs/v2.yaml	
	in API POST /api/v0/b2b/enroll/{readable_id}/
		added the new 'b2b-error-not-enrollable' enum value to the 'result/allOf[#/components/schemas/ResultEnum]/' response property for the response status '200'
		Adding new enum values to response could be unexpected for clients, use x-extensible-enum instead.

info	[endpoint-added] at head/openapi/specs/v2.yaml	
	in API GET /api/v3/program_enrollments/
		endpoint added

info	[endpoint-added] at head/openapi/specs/v2.yaml	
	in API GET /api/v3/program_enrollments/{program_id}/
		endpoint added



Unexpected changes? Ensure your branch is up-to-date with main (consider rebasing).

@odlbot odlbot merged commit 80c4faa into release Feb 5, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants