Skip to content

ci: release-please picked patch bump despite feat(theme): commits #253

Description

@krisarmstrong

Observation

The brand-migration PR #247 included multiple `feat(theme):` commits (Phase 1–5 of the 2026-05-22 audit). Conventional Commits says `feat:` should trigger a MINOR bump. But release-please opened PR #249 with title `chore(main): release 0.16.1` — a PATCH bump.

Seed and NIAC both got minor bumps from the same shape of commit history (Seed 0.194.x → 0.195.0; NIAC → 0.81.0).

Likely causes

  • A `release-please-config.json` override (`bump-minor-pre-major: false` or similar)
  • A .release-please-manifest.json pinning the version
  • A different release-type than the other two products

Acceptance criteria

  • Confirm whether the patch bump was intentional config (and document why)
  • If not intentional, fix the release-please config so feat: commits trigger minor bumps consistently with Seed/NIAC

References

  • Stem release PR chore(main): release 0.17.0 #249 (chore(main): release 0.16.1)
  • Seed release PR #1076 (chore(main): release 0.195.0)
  • NIAC release PR #654 (chore(main): release 0.81.0)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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