Skip to content

v0.140.0

Choose a tag to compare

@davidfarah-dev davidfarah-dev released this 03 Nov 22:08
ca70dd5

Install or update: npm i -g cotal-ai@0.140.0

Changes in this release

  • cotal history limit now sets the limits of DMs and of the delivery daemon's inbox and stored copies as well as channel posts, and takes none for any age or count. --inbox-max-age and --inbox-per-agent set the inbox and stored copies together, and --dm-max-age and --dm-per-sender set DMs. A new space keeps 1000 stored copies per agent and every DM, as before, and cotal up and connecting never change a limit. A lower limit shows what it deletes for each agent or DM pair and asks first. With no limit flags the command prints the four streams' limits and changes nothing. Its --json result now lists one entry per stream under result.streams. Restore brings back the recorded limits of all four streams.

    The delivery daemon stamps each stored copy with the count it was stored under in a Cotal-Delivery-Limit header, and the stored-copies notice compares against that count. A copy without the header counts as 1000.

    In @cotal-ai/core, the chat-only limit API is replaced by one that takes the stream. ChatHistoryLimit becomes HistoryLimit, whose perSender is now perSubject; setChatHistoryLimit, describeChatHistory, chatHistoryLimitProblem, chatHistoryLimitOf and chatHistoryRestoreStaging become setHistoryLimit, describeHistoryLimit, historyLimitProblem, historyLimitOf and historyLimitRestoreStaging; and ChatHistoryChange, ChatHistoryUpdateUnknown and ChatHistoryChanged become HistoryLimitChange, HistoryLimitUpdateUnknown and HistoryLimitChanged. isAcceptedChatHistory, CHAT_HISTORY_MIN_AGE_MS and CHAT_HISTORY_MAX_AGE_MS are removed; historyLimitMinAgeMs and HISTORY_MAX_AGE_MS give the bounds, and historyAgeProblem checks an age on its own, where 0 is an age below the floor. The stored-copies-full event now carries the stamped limit.

  • The manager now calls core's managedRetirementOpId directly at its eight retirement sites. The private retireOpId alias, whose whole body called that function, is gone along with its second copy of the contract. The doc on managedRetirementOpId now also says the id is 26 hex characters, so it is itself a lifecycle token. No behavior changes.

  • The auth package's option types now take the data account as ServiceKeys["dataAccount"] instead of restating { pub: string; signingSeed: string } across its consumers, so a change to what the auth service holds of the data account reaches every declaration that receives it. No runtime change.

What's Changed

  • refactor(manager): call managedRetirementOpId directly by @davidfarah2003 in #5781
  • feat!: history limits for DMs and the delivery streams, and none by @davidfarah2003 in #5767
  • refactor(auth): share the data-account projection type by @davidfarah2003 in #5784
  • docs: name 0.139.1 as the last release without the wider history limits by @davidfarah2003 in #5783
  • chore(release): version packages by @davidfarah2003 in #5782

Full Changelog: v0.139.1...v0.140.0