Skip to content

fix(news): release compile_brief description correction#609

Merged
biwasxyz merged 1 commit into
mainfrom
fix/606-release-description
Jul 16, 2026
Merged

fix(news): release compile_brief description correction#609
biwasxyz merged 1 commit into
mainfrom
fix/606-release-description

Conversation

@biwasxyz

Copy link
Copy Markdown
Collaborator

Refs #606. No file changes — this exists only to trigger a release.

Why

12c6670 (#608) corrected the news_publisher_compile_brief description to match agent-news#869, but was typed docs:. release-please's default node config treats docs as not user-facing, so it skipped the release:

✔ Considering: 1 commits
✔ No user facing commits found since fd21ef13... - skipping

release_created was false and the publish job skipped, so the corrected description is on main but not on npm — it reaches no agent. Meanwhile the stale description is live and tells publisher agents to make the exact call agent-news#869 now rejects with a 400.

fix: was the right type for #608. A tool description is the contract an agent consumes, not documentation about the product — that's #606's whole thesis, and docs: asserts the opposite. Same reasoning made feat: correct for #605's quality_score param.

Why an empty commit

  • workflow_dispatch + publish_existing is dead: 1.64.0 is already on npm, so the publish step's npm view guard skips it.
  • Rewording 12c6670 in place needs a force-push, which the ruleset blocks (non_fast_forward, required_linear_history).

An empty fix: commit is release-please's standard remedy for a mislabeled commit. It should cut 1.64.1 and publish #608's description with it.

12c6670 corrected the news_publisher_compile_brief description to match
agent-news#869 but was typed docs:, so release-please classified it as
not user-facing and skipped the release. The description is the contract
agents consume.

Refs #606
@biwasxyz
biwasxyz merged commit 53761a5 into main Jul 16, 2026
5 checks passed
@biwasxyz
biwasxyz deleted the fix/606-release-description branch July 16, 2026 06:35
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