Skip to content

YipYap (Language) v0.3.5

Choose a tag to compare

@magneum-co magneum-co released this 07 Sep 15:49
· 3 commits to main since this release
Immutable release. Only release title and notes can be modified.

YipYap (Language) v0.3.5

Signed sequence-8 release of the provider-neutral YipYap (Language) plugin.
This release changes publisher display metadata only: the author name in both
provider manifests and the owner and description of the public marketplace
catalogs now read MagneumCo, matching the organization that hosts the official
repository. No connector behavior, scope, callable, event kind, wire field,
teaching meaning, origin, credential binding, or updater pin changes.

Included

  • publisher display name MagneumCo in the Claude and Codex plugin manifests
    and in the yipyap marketplace catalogs;
  • the unchanged compiled future-production profile at
    https://api.magneum.co, the same five authenticated provider callables plus
    the explicit pairing bootstrap, and the same connector-interface packet;
  • the unchanged updater pin MagneumCo/yipyap-language and the declared
    Node.js requirement of 22.23.1 or later.

Upgrade boundary

v0.3.4 installations may accept signed sequence 8 through the normal update
rules; v0.3.3 and earlier updaters still pin the previous repository location
and cross by a provider-native marketplace update or reinstall. Successful
apply stops at restart-required; activation requires a complete provider
restart and a new root task.

Security and privacy

Conversation text, prompts, transcripts, files, repository context, account
identities, provider-session identifiers, credentials, and learner evidence
remain outside the connector payload.

Verification

The clean pushed source passes the repository validator and 306/306 tests
under Node 22.23.1 and under Node 26.5.0. Two independently sourced
signing-key copies produced byte-identical expanded trees, manifests,
detached signatures, deterministic archives, and plugin-root archives.

Not claimed

Publication does not prove provider activation, account connection, pairing,
Learning Mode, restart/new-root acceptance, migration of any installation,
rollback, provider-directory submission, or a public directory card.