Skip to content

chore: brand-name canon + apex URL sweep + repo hygiene#2

Merged
sansware merged 1 commit into
mainfrom
chore/openapi-spec-canon-2026-06-28
Jun 28, 2026
Merged

chore: brand-name canon + apex URL sweep + repo hygiene#2
sansware merged 1 commit into
mainfrom
chore/openapi-spec-canon-2026-06-28

Conversation

@sansware

Copy link
Copy Markdown
Contributor

Summary

  • Brand canon (§3): rename info.title from "TicketWave Access API" to "TicketWave API". This is the headline canon violation — the spec is the most-vendored surface and every downstream SDK was inheriting the wrong product name.
  • Apex URL sweep: all www.ticketwavehq.com references swept to the apex ticketwavehq.com (info.contact.url, info.license.url, servers[1], info.description, securitySchemes.apiKey.description, README License section, CHANGELOG footer reference).
  • Spec version bump: 1.0.01.0.1 with a CHANGELOG entry. No wire-format changes — downstream clients are unaffected.
  • Repo hygiene: validate CI (Redocly lint + swagger-cli on PRs), CONTRIBUTING.md, Contributor Covenant 2.1 CODE_OF_CONDUCT.md, CODEOWNERS (* @sansware), SECURITY.md routing to security@ticketwavehq.com, .github/ISSUE_TEMPLATE/spec-discrepancy.yml, and a fenced JSON-LD Organization schema at the bottom of the README.

Test plan

  • npx @apidevtools/swagger-cli validate openapi.yaml → passes
  • npx @redocly/cli lint openapi.yaml → valid (5 pre-existing warnings, no new ones)
  • No www.ticketwavehq.com references remain in spec/README/CHANGELOG except the CHANGELOG line that describes this sweep
  • info.title reads "TicketWave API"; info.version reads "1.0.1"
  • CI workflow runs green on this PR
  • After merge: tag v1.0.1 and confirm SDK regen picks up the new title

Aligns the OpenAPI spec with brand canon (rename "TicketWave Access API"
to "TicketWave API") and sweeps all www.ticketwavehq.com references to
the apex ticketwavehq.com. Bumps spec version 1.0.0 to 1.0.1.

Also adds standard repo hygiene: validate CI, CONTRIBUTING, CODE_OF_CONDUCT
(Contributor Covenant 2.1), CODEOWNERS, SECURITY, a spec-discrepancy issue
template, and a JSON-LD Organization schema in the README.

No wire-format changes; downstream SDKs are unaffected.
@sansware sansware merged commit f8dc295 into main Jun 28, 2026
1 check passed
@sansware sansware deleted the chore/openapi-spec-canon-2026-06-28 branch June 28, 2026 15:04
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.

1 participant