Skip to content

release: 0.6.3 -> 0.6.4#533

Closed
coseto6125 wants to merge 2 commits into
mainfrom
release/0.6.4
Closed

release: 0.6.3 -> 0.6.4#533
coseto6125 wants to merge 2 commits into
mainfrom
release/0.6.4

Conversation

@coseto6125
Copy link
Copy Markdown
Owner

Automated release bump by scripts/release/cut-release.sh.

  • workspace + ecp-core/ecp-analyzer/ecp-mcp version: 0.6.30.6.4 (patch)
  • CHANGELOG.md updated from conventional commits since v0.6.3

On merge, run scripts/release/cut-release.sh --tag on main to push v0.6.4,
which triggers release.yml (5-platform build + GitHub Release + npm/PyPI publish).

@coseto6125 coseto6125 added the release Automated version-bump / Release PR label Jun 3, 2026
@coseto6125 coseto6125 enabled auto-merge (squash) June 3, 2026 07:40
@coseto6125 coseto6125 added the merge-queue Opt-in to Mergify merge queue label Jun 3, 2026
Replace the auto-generated 'no user-facing changes' placeholder — the skill
ships with the binary and is agent-facing, so it warrants a CHANGELOG line.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2026

ecp impact cache (0 symbols) — internal, used by ecp dev pr-analyze

[]

@coseto6125
Copy link
Copy Markdown
Owner Author

Superseded by the v0.6.4 PR that also includes the build concurrency cap.

@coseto6125 coseto6125 closed this Jun 3, 2026
auto-merge was automatically disabled June 3, 2026 08:37

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ecp:risk-low ecp signal merge-queue Opt-in to Mergify merge queue release Automated version-bump / Release PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant