Repository navigation
chore: bump version to 0.0.2 for protean 0.0.2 - #92
Merged
Merged
Conversation
- protean 0.0.2 is out; the console tag v0.0.2 marks the state verified against it, and the tag must match package.json, as v0.0.1 did - the one console-facing wire change in protean 0.0.2 is the `ready` ack, which the console already reads (#63): its seven fields match StreamReady one for one; the rest of that release is MCP-only - the changelog note still said no release was tagged, which stopped being true at v0.0.1; it now says what the tags mean Co-Authored-By: htjulia <htjulia1@gmail.com>
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.
Why
protean 0.0.2 was released on 2026-10-31. The console marks the protean release it was verified against with a
v*tag that matchespackage.json—v0.0.1did this for protean 0.0.1. This PR moves the version to0.0.2sov0.0.2can be pushed on the merge commit.What changed
package.json/package-lock.json:0.0.1→0.0.2.CHANGELOG.md: the note said "No tagged release yet", which has been false sincev0.0.1. It now states what the tags mean. Entries are not split per tag.Verification against protean 0.0.2
readyacknowledgement reaches the console. The console already reads it (feat(stream): read the connection ack instead of assuming it #63).org.htcom.protean.web.StreamReadyatv0.0.2has seven fields (platform,platformVersion,tracesEnabled,metricsEnabled,buffered,tickMs,capacity), and they matchsrc/lib/types.tsone for one. The other change moves MCP tool errors into_meta. That is MCP-only, and the console does not speak MCP.main(a53b568), run locally:lintpassed (warnings only, no errors).buildpassed.testpassed: 20 files, 245 tests.mainin CI: the last push run (chore(deps): bump nine npm packages in one branch #91) is green.After merge
An annotated tag
v0.0.2("protean v0.0.2 support") goes on the squash commit.v*tags are immutable under therelease-version-tagsruleset. No GitHub Release is created.