Version Packages - #304
Merged
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tangle-network/agent-interface@2.6.0
Minor Changes
8491351: feat(agent-interface):
agentCandidateLineageSchemaaccepts a frontier-authored candidateAgentCandidateLineage.sourcegainsfrontier-author: a profile one agent wrote for another. That is a shipped capability — a supervising agent authors a child's fullAgentProfilefrom inside a run and may promote it to a sub-supervisor — and no existing member described it.optimizerwas the closest and was closed to this caller by its own refinement, which mandates adevelopmentSplitDigest; a run-time author has no held-out split, so the field could only be satisfied by fabricating a digest or by declaringhuman.The member is
frontier-author, the wordAgentProfileDiff.source.kindalready uses for the same actor, so the two enums name one thing with one word rather than two.generatedCandidateSourcesandisGeneratedCandidateSourceare new exports and the single owner of "this candidate was produced from a parent". Three call sites — the lineage refinement and both experiment schemas — branched onoptimizer || compoundindependently, so a new generated source was exempt from the "name your baseline" rule in two of them; they now read one list. The development split stays required byoptimizerandcompoundonly.Additive: every lineage that parsed before parses unchanged.