Skip to content

Skip changelog check for new services#66

Merged
jonathan343 merged 4 commits into
developfrom
skip-changelog-new-service
Jun 25, 2026
Merged

Skip changelog check for new services#66
jonathan343 merged 4 commits into
developfrom
skip-changelog-new-service

Conversation

@jonathan343

@jonathan343 jonathan343 commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

Overview

The api-changelog-check.yml workflow currently detects when an AWS service model in codegen/aws-models is updated. Updated service models require a corresponding changelog entry describing the related changes (usually comes from the upstream service team). The workflow will fail if it doesn't see a new api-change entry under clients/aws-sdk-<service>/.changes/next-release/.

Problem

When a new service is added under codegen/aws-models, the workflow fails with an error similar to the one below:

- qbusiness (directory does not exist: clients/aws-sdk-qbusiness/.changes/next-release)

Our release infra automatically handles creating a new changelog entry for new services, so this is something we don't need to worry about here.

Solution

When a new service model is added, we'll skip the check since it's intended for updated service models only.

Testing

I pushed a new-service.json file and the workflow ran successfully (src):

Skipping new service 'new-service' (no package yet; changelog generated through release infra).
All modified models have corresponding changelog entries.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jonathan343 jonathan343 requested a review from a team as a code owner June 25, 2026 05:23
@jonathan343 jonathan343 merged commit d3ee58a into develop Jun 25, 2026
3 checks passed
@jonathan343 jonathan343 deleted the skip-changelog-new-service branch June 25, 2026 14:36
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.

2 participants