Skip to content

chore: release 5.4.1 - #145

Merged
finalerock44 merged 1 commit into
productionfrom
promote/cli-5.4.1
Sep 10, 2026
Merged

chore: release 5.4.1#145
finalerock44 merged 1 commit into
productionfrom
promote/cli-5.4.1

Conversation

@finalerock44

Copy link
Copy Markdown
Contributor

Promote from dev to stable: iOS 27 in the --ios-version enum (#131/#134 — the iPhone 17 devices were already dropped), bplist-parser 0.5 named exports (#143), the CLA action fork (#135/#136) and the grouped dependency bumps.

Release-As: 5.4.1 because the promotion commit is a chore: and would otherwise cut no release at all. 5.4.1 rather than the 5.5.0 the iOS 27 feat: would roll, so the stable line matches the beta line already published as 5.4.1-beta.1.

Carries only the source delta — package.json version, CHANGELOG.md and the release-please manifests stay as release-please left them on production.

Release-As: 5.4.1

What & why

Type of change

  • fix — bug fix
  • feat — new feature
  • perf — performance improvement
  • refactor — code change that's neither a fix nor a feature
  • docs — documentation only
  • chore / ci / build / test — tooling, no user-facing change
  • Breaking change (title has ! or PR notes a BREAKING CHANGE:)

Checklist

  • PR title follows the Conventional Commits format (see comment above)
  • pnpm lint passes
  • pnpm typecheck passes
  • pnpm build passes
  • I have not bumped the version or edited CHANGELOG.md (release-please handles this)
  • I have signed the CLA (the bot will prompt on first contribution)
  • Docs / README.md / STYLE_GUIDE.md updated if behaviour or output changed

How to test

@finalerock44 finalerock44 self-assigned this Sep 10, 2026
Promote from dev to stable: iOS 27 in the `--ios-version` enum (#131/#134 —
the iPhone 17 devices were already dropped), bplist-parser 0.5 named exports
(#143), the CLA action fork (#135/#136) and the grouped dependency bumps.

`Release-As: 5.4.1` because the promotion commit is a `chore:` and would
otherwise cut no release at all. 5.4.1 rather than the 5.5.0 the iOS 27 `feat:`
would roll, so the stable line matches the beta line already published as
5.4.1-beta.1.

Carries only the source delta — package.json version, CHANGELOG.md and the
release-please manifests stay as release-please left them on production.

Release-As: 5.4.1
@finalerock44
finalerock44 merged commit 19dcbad into production Sep 10, 2026
5 checks passed
@finalerock44
finalerock44 deleted the promote/cli-5.4.1 branch September 10, 2026 15:57
finalerock44 added a commit that referenced this pull request Sep 10, 2026
Second promotion commit for 5.4.1: #145 carried dev as of this morning, and the
notices change (#147) landed on dev after it. Source delta only; package.json
version, CHANGELOG.md and the release-please manifests stay as production has
them so release-please re-renders #146 with this entry added.

* feat(notices): expose platform, device and Maestro version to notice targeting; include notices in --json output (#147)

Release-As: 5.4.1
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