Repository navigation
chore: add requestId to generated ChargeRunRequest from OpenAPI spec - #1171
Merged
Merged
Conversation
apify-service-account
added
the
t-tooling
vdusek
changed the title
vdusek
enabled auto-merge (squash)
October 23, 2026 17:10
vdusek
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
src/generated/api.tsandsrc/generated/schemas.tsfrom the published OpenAPI specification, and records its version inpackage.json.v2-2026-10-20T095308Z->v2-2026-10-22T124802Z.Important
Retitle this pull request to
fix:orfeat:when the diff is user-facing, so that it lands in the changelog and triggers a release -chore:does neither.Note
A red check here is a guard in
src/spec_guards.tsdoing its job: a field an override block replaces was dropped or renamed, a documented spec gap was filled and its*SpecGapsentry is now stale, a shared@apify/constsenum diverged, or a generated zod schema stopped accepting its generated type. Each of those is a decision, not a mechanical update. A failingfixtures.test.tsmeans the specification now requires something the mock fixtures intest/mock_server/fixtures.tsdo not carry.