feat: add message param and error responses to createTicket

[biilmann]

Summary

• Add message parameter to the createTicket endpoint request body for OAuth ticket creation
• Add 401 (Unauthorized) and 422 (Unprocessable Entity) error response schemas to createTicket
• Bump version to 2.51.0 to match release
• Rebuild Go client with updated models

Test plan

• CI passes (npm test — lint, build, unit tests)
• Go client compiles with new models
• Verify createTicket endpoint accepts message in request body

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for open-api ready!

Name	Link
🔨 Latest commit	2ea690d
🔍 Latest deploy log	https://app.netlify.com/projects/open-api/deploys/69b1d9c20fe0470008e465fe
😎 Deploy Preview	https://deploy-preview-632--open-api.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 74d245da-fcca-4ce2-b261-ba28af03cbb0

📥 Commits

Reviewing files that changed from the base of the PR and between 6c485a0 and 6ded4ef.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• go/models/create_ticket_params_body.go
• go/plumbing/operations/create_ticket_parameters.go
• go/plumbing/operations/create_ticket_responses.go
• package.json
• swagger.yml

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• New Features

  • The POST /oauth/tickets endpoint now accepts a message field in the request body, allowing clients to create tickets with enhanced messaging capabilities.

• Bug Fixes

  • Improved error handling with proper HTTP response codes: 401 Unauthorized when OAuth application is not found, and 422 Unprocessable Entity for validation errors.

Walkthrough

This pull request adds request body support and error response handling to the POST /oauth/tickets endpoint. A new Go model CreateTicketParamsBody is introduced containing a Message field. The CreateTicketParams operation is updated with a Body field and supporting methods (WithBody, SetBody) to handle request bodies. Response processing is extended to handle 401 (Unauthorized) and 422 (Unprocessable Entity) error cases with dedicated response types. The API version is incremented from 2.50.0 to 2.51.0 in package manifests and the OpenAPI specification is updated to document the request body schema and new error responses.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• feat: add message param and error responses to createTicket #630 — Directly overlaps with this PR by modifying the same POST /oauth/tickets endpoint and generating identical Go files (CreateTicketParamsBody, CreateTicketParameters, CreateTicketResponses) with body parameter support and 401/422 error response handling.

Suggested reviewers

• sean-roberts

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main changes: adding a message parameter and error responses to the createTicket endpoint.
Description check	✅ Passed	The description clearly outlines the key objectives—adding message parameter, error responses, version bump, and Go client rebuild—and is directly related to the changeset.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/oauth-tickets-message-and-errors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}