Repository navigation
release: prepare v0.8.0 - #39
Merged
Merged
Conversation
Bump the service version to 0.8.0 across package.json, package-lock.json, and SERVICE_VERSION, and turn the Unreleased changelog into a grouped 0.8.0 entry that leads with client-visible changes, including the new query rejection on parameterless routes and the longer validation messages. A minor bump because clients that append query strings to parameterless routes, or match exact old validation message text, must adapt. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
10 tasks done
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.
Goal
Prepare v0.8.0, following the convention of #35: version bump in
package.json,package-lock.json, andSERVICE_VERSION, plus a dated changelog entry.Scope / non-goals
Changed: version 0.7.0 to 0.8.0, the
Unreleasedchangelog regrouped into a dated 0.8.0 entry that leads with client-visible changes, and the README agent example'sservice_version.Not changed: any runtime behavior. This PR does not deploy anything. Candidate upload, zero-percent smoke, promotion, and the GitHub release remain the human-gated flow in
docs/RELEASE.md. The README's "Supported release" line stays onv0.6.2until production actually moves, as in #33.Public contract
Minor bump because of two client-visible changes already merged in #36:
/,/v1/health,/v1/categories,/v1/stats, and/openapi.jsonnow return400 INVALID_REQUEST.codefield is unchanged.Both are called out at the top of the changelog entry.
Security impact
Verification
npm run verify(94 tests)git diff --checkinfo.versionfollowsSERVICE_VERSION🤖 Generated with Claude Code