fix(news): release compile_brief description correction#609
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #606. No file changes — this exists only to trigger a release.
Why
12c6670 (#608) corrected the
news_publisher_compile_briefdescription to match agent-news#869, but was typeddocs:. release-please's default node config treatsdocsas not user-facing, so it skipped the release:release_createdwas false and thepublishjob skipped, so the corrected description is onmainbut 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, anddocs:asserts the opposite. Same reasoning madefeat:correct for #605'squality_scoreparam.Why an empty commit
workflow_dispatch+publish_existingis dead: 1.64.0 is already on npm, so the publish step'snpm viewguard skips it.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.