@sentry/junior-linear 0.267.0 → 0.269.0

package/README.md

@@ -1,43 +1,16 @@
 # @sentry/junior-linear
 
-`@sentry/junior-linear` adds Linear issue workflows to Junior through Linear's hosted MCP server.
-
-Install it alongside `@sentry/junior`:
+Linear issue workflows and issue events for Junior through Linear's hosted MCP server.
 
 ```bash
 pnpm add @sentry/junior @sentry/junior-linear
 ```
 
-Then add the plugin to the set exported from `plugins.ts`:
-
-```ts title="plugins.ts"
+```ts
 import { defineJuniorPlugins } from "@sentry/junior";
 import { linearPlugin } from "@sentry/junior-linear";
 
 export const plugins = defineJuniorPlugins([linearPlugin()]);
 ```
 
-This package does not require a shared `LINEAR_API_KEY` or a custom OAuth app for the default setup. Each user connects their own Linear account the first time Junior calls a Linear MCP tool. Junior sends the authorization link privately and resumes the same Slack thread automatically after the user authorizes.
-
-Optionally, a Junior admin can connect a Linear service account from the dashboard Admin page, or with `junior service-account connect linear`. The plugin lets that account call only Linear's read tools, such as `get_issue`, `list_issues`, and `list_comments` (`accounts.service-account.tools`). Users who have not connected Linear then use that account for those tools. Creating or updating issues and comments still asks the user to connect their own account. Anyone who can talk to Junior can read what the service account can read.
-
-Linear operations use Linear's hosted MCP tools directly. When an issue is created through that path, Junior links it to the current conversation.
-
-To run watches or event automations when Linear issues are created:
-
-1. Set `LINEAR_WEBHOOK_SECRET` to the Linear webhook signing secret.
-2. Create a Linear webhook for the `Issue` resource at `https://<junior-host>/api/webhooks/linear`.
-3. Redeploy Junior.
-
-The plugin verifies the `Linear-Signature` header and publishes `issue.created` for the issue identifier and the team key. Team event automations use the Linear team key, such as `SRE`. Issue and team watches also accept an optional `match.teamKey` filter on trusted event data.
-
-Optional: set channel defaults when a Slack thread usually routes work to the same Linear destination:
-
-```bash
-jr-rpc config set linear.team Platform
-jr-rpc config set linear.project "Cross-team reliability"
-```
-
-These defaults are only fallbacks. If the user names a different team or project in the request, Junior should follow the explicit request instead.
-
-Full setup guide: https://junior.sentry.dev/extend/linear-plugin/
+Setup and configuration: https://junior.sentry.dev/extend/linear-plugin/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sentry/junior-linear",
-  "version": "0.267.0",
+  "version": "0.269.0",
   "private": false,
   "publishConfig": {
     "access": "public"
@@ -23,7 +23,7 @@
   ],
   "dependencies": {
     "zod": "^4.5.4",
-    "@sentry/junior-plugin-api": "0.267.0"
+    "@sentry/junior-plugin-api": "0.269.0"
   },
   "devDependencies": {
     "@oxlint/plugins": "1.79.0",