@checkstack/integration-teams-backend 0.0.32 → 0.0.34

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,48 @@
1
1
  # @checkstack/integration-teams-backend
2
2
 
3
+ ## 0.0.34
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [f23f3c9]
8
+ - Updated dependencies [f23f3c9]
9
+ - Updated dependencies [f23f3c9]
10
+ - @checkstack/common@0.11.0
11
+ - @checkstack/backend-api@0.17.0
12
+ - @checkstack/integration-backend@0.1.29
13
+
14
+ ## 0.0.33
15
+
16
+ ### Patch Changes
17
+
18
+ - a06b899: Template autocomplete on Jira template fields, plus a sweep of dead code across integration / notification plugins.
19
+
20
+ **FIXES**
21
+
22
+ - Jira subscription dialog now offers `{{ payload.* }}` autocomplete on its three template fields (`summaryTemplate`, `descriptionTemplate`, field-mapping `template`). Each was declared as `configString({})` with empty metadata, so `DynamicForm` fell through to a plain `<Input>` and the `templateProperties` chain that `CreateSubscriptionDialog` already pipes in from the event's payload schema bypassed them entirely. Tagged all three with `"x-editor-types": ["raw"]` so they now route through `MultiTypeEditorField` → `RawEditor` (the textarea with the `{{ … }}` popup) — the same path webhook templates already used.
23
+
24
+ **INTERNAL CLEANUP — dead code removed**
25
+
26
+ Every removal here was verified with a repo-wide `grep` for external consumers; nothing in this changeset alters a public surface that anyone actually imports.
27
+
28
+ - `@checkstack/integration-jira-common`:
29
+ - Deleted `src/rpc-contract.ts` entirely. The Jira-specific `jiraContract` / `JiraApi` (connection-CRUD endpoints — `listConnections`, `getConnection`, `createConnection`, `updateConnection`, `deleteConnection`, `testConnection`) was never registered with the backend router and had zero client consumers. All connection management goes through the generic `integrationContract` in `@checkstack/integration-common`.
30
+ - Removed seven dead Zod schemas + their inferred types from `src/schemas.ts`: `CreateJiraConnectionInputSchema`, `UpdateJiraConnectionInputSchema`, `JiraConnectionRedactedSchema`, `JiraFieldMappingSchema`, `JiraSubscriptionConfigSchema`, `JiraConnectionSchema`, plus their `…Input` / `…Redacted` / `…FieldMapping` / `…Config` / `…Connection` type aliases. The subscription config was duplicated against the canonical, metadata-tagged version in `jira-backend/src/provider.ts`; the connection schemas were marked `@deprecated` and only referenced by the now-removed RPC contract or the deprecated function below.
31
+ - Removed orphaned npm deps `@orpc/contract` and `@checkstack/integration-common` from the package's `dependencies` (they were only used by the deleted RPC contract).
32
+ - `@checkstack/integration-jira-backend`:
33
+ - Removed `createJiraClientFromConnection` from `src/jira-client.ts`. The function was marked `@deprecated` ("Use createJiraClientFromConfig with generic connection management") and had zero callers; removing it dropped the last consumer of `JiraConnection` / `JiraConnectionSchema`. The modern `createJiraClientFromConfig` (using `JiraConnectionConfig` with cloud/datacenter auth modes) is the canonical entry point.
34
+ - `@checkstack/integration-teams-backend` + `@checkstack/integration-webex-backend`:
35
+ - Removed the `// Re-export for testing` blocks from each plugin's `src/index.ts`. The Teams plugin re-exported `teamsProvider` / `TeamsConnectionSchema` / `TeamsSubscriptionSchema` / `buildAdaptiveCard`; the Webex plugin re-exported `webexProvider` / `WebexConnectionSchema` / `WebexSubscriptionSchema`. Both `provider.test.ts` files were retargeted from `./index` to `./provider`, eliminating the indirection and matching the convention used by the other backend-only integration plugins.
36
+ - `@checkstack/notification-telegram-backend`:
37
+ - Removed the broken `bundle` field from `package.json` that referenced `@checkstack/notification-telegram-common` and `@checkstack/notification-telegram-frontend` — neither package existed (the directories were empty leftovers with no `package.json`, so not even workspace members). The empty directories were deleted; `bun install` is clean afterwards. `bunx @checkstack/scripts plugin-pack` for this plugin would otherwise have tried to bundle non-existent packages.
38
+
39
+ No tests changed behaviour. 2040 tests pass, lint + typecheck clean.
40
+
41
+ - Updated dependencies [a06b899]
42
+ - Updated dependencies [a06b899]
43
+ - @checkstack/backend-api@0.16.0
44
+ - @checkstack/integration-backend@0.1.28
45
+
3
46
  ## 0.0.32
4
47
 
5
48
  ### Patch Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@checkstack/integration-teams-backend",
3
- "version": "0.0.32",
3
+ "version": "0.0.34",
4
4
  "type": "module",
5
5
  "main": "src/index.ts",
6
6
  "checkstack": {
@@ -14,8 +14,8 @@
14
14
  "pack": "bunx @checkstack/scripts plugin-pack"
15
15
  },
16
16
  "dependencies": {
17
- "@checkstack/backend-api": "0.15.2",
18
- "@checkstack/integration-backend": "0.1.26",
17
+ "@checkstack/backend-api": "0.16.0",
18
+ "@checkstack/integration-backend": "0.1.28",
19
19
  "@checkstack/common": "0.10.0",
20
20
  "zod": "^4.2.1"
21
21
  },
package/src/index.ts CHANGED
@@ -14,11 +14,3 @@ export default createBackendPlugin({
14
14
  extensionPoint.addProvider(teamsProvider, pluginMetadata);
15
15
  },
16
16
  });
17
-
18
- // Re-export for testing
19
- export {
20
- teamsProvider,
21
- TeamsConnectionSchema,
22
- TeamsSubscriptionSchema,
23
- buildAdaptiveCard,
24
- } from "./provider";
@@ -4,7 +4,7 @@ import {
4
4
  TeamsConnectionSchema,
5
5
  TeamsSubscriptionSchema,
6
6
  buildAdaptiveCard,
7
- } from "./index";
7
+ } from "./provider";
8
8
 
9
9
  /**
10
10
  * Unit tests for the Microsoft Teams Integration Provider.