Skip to content

Ta 4.14.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 07:36
· 3 commits to main since this release

Minor Changes

  • Who else is in your Ta, and where (docs/design/ta-team.md 15): each page tells what conversation it shows and whether its user types (TaPresenceServer.report), and ta serve tells the others with the list of sessions (TaSessionInfo.people), only of the conversations each may see. The top of a conversation shows the faces of those looking at it, the line over its box who types and whom Ta answers, a row of the list who looks at it and whose message it answers, and Members where each one is, with Follow. A message of one let in carries who wrote it (TaMessageAuthor, written by ta serve alone) and shows on the left with their face and name; a waiting one is taken back by its author or the owner alone. TaExtensionHost.presence() gives people. (@celljs/ta-client, @celljs/ta-host, @celljs/ta-protocol, @celljs/ta-team, @celljs/ta-web)
  • Signing in with an account from the Ta app, and setting the ways to sign in up in Settings. The join dialog of the Ta app offers the ways of the Ta of the link: it opens the page of the link in the system browser with a handoff id (RelayTeamLinkUtil.signInFor), which signs in there and hands the account to that Ta (signedIn); the app takes it back (handedOff) and asks with it, once. Settings → Access → Ways to sign in sets up GitHub, Google, WeChat and an OpenID Connect provider in sign-in.json (TaAccessServer.getSignInConfig / setSignInProvider, for the owner alone: the new rule owner), offered at once, the secret never read back, with the callback URL to register; one the environment sets is shown, not changed. (@celljs/ta-host, @celljs/ta-protocol, @celljs/ta-relay, @celljs/ta-team, @celljs/ta-web)
  • Members who sign in with an account. The page of joining of a link offers the ways this Ta signs in with (GitHub, Google, WeChat, OpenID Connect; the environment or the new sign-in.json of the agent directory): the provider sends the browser back to the relay's /j, and the owner's ta serve alone turns the code into the account (TaHostTeam.accounts, PKCE and the secret never leave it). Requests and members keep their account; the same account coming again, by any browser or link, is the same member. A link may ask everyone to sign in, or let in some accounts alone (google:*@example.com). One from a browser signed in with an account may manage members; without one, still not. Dialogs of Ta's web page scroll their content when it is taller than the window. (@celljs/ta-host, @celljs/ta-protocol, @celljs/ta-relay, @celljs/ta-team, @celljs/ta-web)

Patch Changes

  • The daily brief of ta-recall reads the notices of ta-notify, the runs of ta-cron and the proposals of ta-initiative by calling their hosts (notices(), list() / runs(), the new proposals()), no longer by their data keys. The README of ta-web and the ta-package skill list openLink, registerInitiative, ui.connect and ui.useAsks. (@celljs/ta-cron, @celljs/ta-extensions, @celljs/ta-initiative, @celljs/ta-notify, @celljs/ta-recall, @celljs/ta-web)
  • One without Ta joins another's Ta from a browser (docs/design/ta-team.md 16): a link that invites (/j#…) opens the page of joining of the relay, which asks with a name and, once let in, opens Ta's web page the relay serves under /w/ (ta relay serves it from its own files; the Worker from its assets), signed in with #pair=. The handshake of joining is the relay's (RelayTeamJoining, RelayTeamLinkUtil, RelayTeamSeal, RelayHostCalls), shared with the Ta app. One who came in from a browser is marked so in Members and never gets a role or grant that manages members. Ta's web page signs in with a pairing link in #pair= of its address. Scheduled tasks no longer leave an unhandled error in the page of one who may not see them. (@celljs/ta-cron, @celljs/ta-harness, @celljs/ta-relay, @celljs/ta-team, @celljs/ta-web)
  • One look across the pages of Ta: the segmented controls of Members and permissions, the editor of a post and the preview of the workbench are the page's; the empty states of Suggestions, Friends and Moments are the EmptyState of every page; Chinese in Sync and Nearby breaks between words; ta serve --help and ta gateway --help wrap at one width. (@celljs/ta-gateway, @celljs/ta-harness, @celljs/ta-initiative, @celljs/ta-moments, @celljs/ta-nearby, @celljs/ta-rooms, @celljs/ta-sync, @celljs/ta-team, @celljs/ta-web, @celljs/ta-workspace, @celljs/ta)
  • A task of the double whose conversation ended asking the user still waits for them once its session closed while idle (read from the saved conversation); when Moments and suggestions were last seen only moves on, whichever page saw them later. (@celljs/ta-initiative, @celljs/ta-moments, @celljs/ta-web)
  • Whether to sign in is for those who join: a link no longer asks everyone to sign in nor lets in some accounts alone (signIn and accounts of invites are gone, and the refusal notListed). Who joins without signing in is anonymous, by the name they give, which Members and the requests say (Anonymous), those signed in by their account. From a browser a role that manages members still wants an account. (@celljs/ta-relay, @celljs/ta-team)
  • Dependencies updated within their major versions: reflect-metadata 0.1.14, cache-manager 5.7.6, jose 4.15.9, cos-nodejs-sdk-v5 2.15.4, lucide-react 1.73.0, marked 14.1.4. The cache manager of @celljs/cache passes on / removeListener for the error events cache-manager 5.7 adds to its caches. pi stays at 1.5.2, its latest release. (@celljs/ta-web, @celljs/ta-workspace, @celljs/ta)

npm i -g @celljs/ta@4.14.0

桌面版:download.cellbang.com/ta,装好后会自己更新。 / The desktop app: download.cellbang.com/ta; it updates itself once installed.

反馈问题 / Report an issue