Skip to content

fix(release)!: release updated models and classify OpenAPI updates - #35

Merged
orest-tokovenko-block merged 1 commit into
mainfrom
fix/openapi-release-classification
Oct 1, 2026
Merged

fix(release)!: release updated models and classify OpenAPI updates#35
orest-tokovenko-block merged 1 commit into
mainfrom
fix/openapi-release-classification

Conversation

@orest-tokovenko-block

@orest-tokovenko-block orest-tokovenko-block commented Oct 1, 2026

Copy link
Copy Markdown
Collaborator

Restore release detection for the model changes merged in #34 and future OpenAPI updates.

Changes

  • Change generated-model commit messages and PR titles from chore: to feat(models):
  • Add instructions to mark incompatible model changes with a breaking-change commit
  • Preserve the existing workflow triggers, action pins, permissions, and regeneration branch

Release impact

  • Mark this recovery commit as breaking to request 3.0.0 from the current 2.2.1
  • PR chore: update OpenAPI spec and regenerate models #34 added required fields to Me, Integration, Budget, and BudgetPerformance, made UnitCost.calculation_type required, and tightened grouping validation
  • Release Please will prepare the version and changelog updates in a separate release PR after this PR merges
  • Publishing still requires merging that release PR

Verification

  • Checked the recovery commit with release-please 17.1.3: fix, breaking, next version 3.0.0
  • Checked the bot's new message with release-please 17.1.3: feat, nonbreaking, minor version increment
  • Validated workflow YAML, shell syntax, commit/title agreement, and unchanged workflow behavior outside release classification
  • YAML lint has no errors; existing document-start, truthy-key, and comment-spacing warnings remain

@orest-tokovenko-block
fix(release)!: release updated models and classify OpenAPI updates
0fe454b 
Request the release missed after PR #34 and classify future generated-model
updates as features instead of chores. Keep breaking-change review explicit.

BREAKING CHANGE: The models merged in #34 require Me.is_account_owner,
Integration.enriched_by, Budget.type, Budget.period_cadence,
BudgetPerformance.type, and UnitCost.calculation_type. Kubernetes and
financial-commitment grouping parameters now reject unsupported values.
Update manually constructed models and grouping inputs before upgrading.
@orest-tokovenko-block
orest-tokovenko-block merged commit 05356aa into main Oct 1, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@orest-tokovenko-block