chore: version packages

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)

[github-actions]

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

@plotday/twister@0.50.0

Added

• Integrations.markNeedsReauth(channelId) for connectors to flag a channel's connection as needing re-authentication when an API call returns a permanent auth-style error (e.g. Slack invalid_auth, token_revoked). The runtime continues to flag reauth automatically on permanent token-refresh failures and on stored-token-missing reads; this method covers cases the runtime can't observe. (ac917ea)
• Store.acquireLock(key, ttlMs) and Store.releaseLock(key) for TTL-aware locks. Replaces the boolean "in progress" flag pattern that connectors had to hand-roll, with self-expiring leases that survive crashed sync attempts. Lock keys live in a reserved namespace and never appear in get / list results. (8f9cbda)
• RUNTIME.md documents the per-twist-instance rate limits (200 invocations / 5 min burst, 500 / 24 h, cost limits) that the platform enforces, the auto-suspension behavior when they are exceeded, and the rule that suspensions are lifted automatically on the next deploy of the twist. Includes guidance on avoiding the most common cause of auto-suspension: unbounded runTask self-chains. (25d2b29)

Changed

• NewScheduleOccurrence.archived renamed to cancelled. Per-instance cancellations now have an explicit semantic distinct from archiving an override row. Connectors should emit cancelled: true for skipped occurrences; the runtime translates these into additions on the parent schedule's recurrenceExdates. (#130a4ee2a8)
• connector re-auth recovery is now automatic. When a user re-authorizes a previously-broken connection (one with needs_reauth_at set), the framework dispatches onChannelEnabled for every channel that was already enabled, with a new SyncContext.recovering = true flag. Connectors should treat the same dispatch as initial-enable (overwrite stored state) but additionally drop persisted incremental cursors / sync tokens so the next pass re-walks history and picks up changes that occurred during the auth gap.
• clarified that Note.key is scoped to a (thread, link) pair, not just a thread. Two links on the same thread can now each carry a note with the same key (e.g. "description") without colliding. No API change — the runtime infers the link from the surrounding saveLink call. (#1358203019)

Removed

• Plot.getDefaultPriorityId(). Connectors and twists no longer have access to a fallback "root" priority. All thread routing happens server-side via classification (which is team-aware as of this release). Twists that need an explicit priority should pull it from their @-mention context (e.g. note.thread.priority.id). (#1366ea5392)