chore: version packages - #751
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
August 31, 2026 10:20
2eb30ce to
989eb24
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 31, 2026 17:56
989eb24 to
0e09bcc
Compare
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 publish to npm yourself or setup this action to publish 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
@sapiom/agent@0.13.0
Minor Changes
PACKAGE_INVENTORY_PROTOCOL,packageInventorySchema, and the public package-inventory types for validating versioned working-tree and immutable-bundle agent inventories.@sapiom/harness@0.12.0
Minor Changes
917c930: Project dependency graphs now open before source-name inspection finishes. They enrich identities in the background, retain per-agent identity warnings without holding an otherwise settled graph out of cache, and keep retryable reads recoverable. Navigation targets are served with the exact graph revision they belong to, so opening an agent from the map lands on the right one.
1107764: Discover markerless
defineAgentand legacydefineOrchestrationprojects plus literal direct source invocations with bounded syntax-only analysis, conservative reconciliation, and live rail/system-graph updates without importing, bundling, type-checking, or executing project code. Public direct invocation edges usebasis: "static-invocation". Markerless agents inside nested Git repositories are discovered when that repository is selected directly; package-wide output-to-input data flow remains a separate evidence provider.Breaking: Public system-graph invocation edges that previously carried
basis: "static"now carrybasis: "static-invocation".Migration: Consumers that validate or deserialize
GET /api/workspaces/:workspaceKey/system-graphresponses must accept"static-invocation"as the invocation-edgebasisvalue before upgrading.a7d4185:
HarnessSettings.helpSeenrecords that the first-run Studio explainer has been dismissed. The flag previously lived in browserlocalStorage, which is keyed by origin; hosts that bind an ephemeral port — the desktop app does, on every boot — presented a new origin with empty storage each launch and re-showed the card every time. It is now per-install and origin-independent, and it survives a reset of the client-sideui-prefsblob.Also fixes
PATCH /api/settingssilently droppingtelemetryNoticeDismissed: the field was absent from the request schema, which strips unknown keys, so the request succeeded and nothing was written. Because nothing was ever stored, there is no earlier dismissal to honour — installs will see the telemetry notice one final time after upgrading, and the next dismissal is the first one that persists.settings.jsongains the key at that point.Patch Changes
@sapiom/agent-core@0.13.3
Patch Changes
@sapiom/agent-runtime@0.7.1
Patch Changes
@sapiom/agent-studio@0.1.21
Patch Changes
@sapiom/cli@11.0.0
Patch Changes
@sapiom/harness-desktop@0.4.2
Patch Changes