Skip to content

[breaking-change] Daily Breaking Change Analysis - 2026-07-17 #46272

Description

@github-actions

Summary

  • Total Breaking Changes: 1
  • Severity: MEDIUM
  • Commits Analyzed: 10
  • Status: Review Recommended

Critical Breaking Changes

Commit File Category Change Impact
e79c5329 pkg/cli/add_command.go Behavior Change gh aw add now errors for packages with aw.yml config instead of installing with a TODO message Scripts/users running gh aw add on packages that declare config steps will now see an error and must switch to gh aw add-wizard
Full Code Diff Analysis

Detailed Commit Analysis

Commit e79c532: Run package manifest config bootstrap flow by default in gh aw add

Before this change, gh aw add <package-with-config> would:

  1. Install the package
  2. Print a TODO message: printBootstrapConfigTODO

After this change, gh aw add <package-with-config> will:

  1. Return an error with message: package X declares aw.yml config and cannot be installed with 'gh aw add'. Use 'gh aw add-wizard X' so the config steps can run interactively

This is a behavior change: previously the operation succeeded (with a warning/TODO), now it fails with a non-zero exit code.

Other commits analyzed (non-breaking)

  • da9762a: Refactor logs download orchestration — internal refactoring only, DownloadWorkflowLogs signature unchanged.
  • 5374e8b: Refactor threat-detection — internal code reorganization, no CLI impact.
  • a4da0c5: Fix linter drift — no CLI impact.
  • 5780279: Enhance GitHub host detection — additive behavior (auto-detect GH_HOST), no removals.
  • b20bbb0: Docs update — no CLI impact.
  • 204195a: Add debug logging — no CLI impact.
  • c096ffe: Docs workshop view — no CLI impact.
  • Schema change in e79c532 (aw_manifest_schema.json): Added new commit-and-push action type — additive, not breaking.

Breaking Change Pattern Detected

Behavior Change: The gh aw add command now rejects packages with aw.yml config sections. Previously it would silently install and print a TODO, now it fails with a non-zero exit code. This breaks any automation or CI scripts that use gh aw add to install such packages.

All Commits Analyzed
SHA Date Message
c096ffe 2026-07-17 docs: add experimental workshop view
da9762a 2026-07-17 Refactor logs download orchestration to reduce pkg/cli largefunc backlog
5374e8b 2026-07-17 refactor(threat-detection): extract shared external detector WorkflowData setup
a4da0c5 2026-07-17 fix: sync pkg/linters/doc.go to 51 analyzers and add drift guard test
b20bbb0 2026-07-17 docs: update glossary - daily scan 2026-07-17
5780279 2026-07-17 Enhance GitHub host detection for PAT creation and setup commands
204195a 2026-07-17 Add debug logging to workflow and CLI helpers
e79c532 2026-07-16 Run package manifest config bootstrap flow by default in gh aw add
38e22c4 2026-07-16 Decouple Process Safe Outputs client token from project-specific token
f7dc268 2026-07-16 feat: add OutcomeStatusLifecycle and OutcomeStatusLifecycleClose as first-class types

Action Checklist

Complete the following items to address these breaking changes:

  • Review all breaking changes detected — Verify the gh aw add behavior change is correctly categorized; this may be intentional.
  • Create a changeset file in .changeset/ directory — Create a file like breaking-aw-add-config-packages.md with major bump type if the behavior change is intentional. See scratchpad/changesets.md for format details.
  • Add migration guidance to changeset — Include instructions: replace gh aw add <package> with gh aw add-wizard <package> for packages that declare aw.yml config.
  • Document breaking changes in CHANGELOG.md — Add entry under "Breaking Changes" section.
  • Verify backward compatibility was considered — Confirm that making gh aw add error (instead of warn) was intentional and alternatives to breaking were evaluated.

Recommendations

Migration steps for affected users:

  • Replace gh aw add <package> with gh aw add-wizard <package> for any package that declares interactive config steps in aw.yml.
  • If running in non-interactive automation, check if the package supports a non-interactive installation path.

Version bump guidance: if this behavior change is intentional, a major version bump is required per the breaking change policy.

Reference

See scratchpad/breaking-cli-rules.md for the complete breaking change policy.


Once all checklist items are complete, close this issue.

⚠️ Compatibility report by Breaking Change Checker · 36.9 AIC · ⌖ 9.9 AIC · ⊞ 5.3K ·

  • expires on Jul 19, 2026, 7:26 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions