Skip to content

Update junior monorepo to v0.266.0 - #248

Merged
jonahsnider merged 3 commits into
mainfrom
renovate/junior-monorepo
Oct 31, 2026
Merged

jonahsnider merged 3 commits into
mainfrom
renovate/junior-monorepo

Conversation

@renovate

@renovate renovate Bot commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@sentry/junior (source) 0.257.0 → 0.266.0 age confidence
@sentry/junior-dashboard (source) 0.257.0 → 0.266.0 age confidence
@sentry/junior-plugin-api (source) 0.257.0 → 0.266.0 age confidence

Release Notes

getsentry/junior (@​sentry/junior)

v0.266.0

Compare Source

New Features ✨
Dashboard
Events
Bug Fixes 🐛
Internal Changes 🔧

v0.265.0

Compare Source

New Features ✨
Dashboard
Github
Sentry
Other
Bug Fixes 🐛
Dashboard
Dev
Other
Documentation 📚
Internal Changes 🔧
Attachments
Dashboard
Events
Sandbox
Other

v0.264.0

Compare Source

New Features ✨
Task Execution
Other
Bug Fixes 🐛
Internal Changes 🔧

v0.263.0

Compare Source

New Features ✨
Bug Fixes 🐛
Documentation 📚

v0.262.0

Compare Source

New Features ✨
Github
Other
Bug Fixes 🐛
Documentation 📚
Internal Changes 🔧

v0.261.0

Compare Source

New Features ✨
Bug Fixes 🐛
Dashboard
Slack
Internal Changes 🔧
Deps
Deps Dev
Other

v0.260.0

Compare Source

New Features ✨
Bug Fixes 🐛
Dashboard
Other
Internal Changes 🔧

v0.259.0

Compare Source

New Features ✨
Internal Changes 🔧

v0.258.0

Compare Source

New Features ✨
Bug Fixes 🐛
Internal Changes 🔧

Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot enabled auto-merge (squash) October 27, 2026 22:12
@vercel

vercel Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
bolt Ignored Ignored Oct 31, 2026 7:37pm UTC

Request Review

@renovate

renovate Bot commented Oct 27, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Error: ERR_PNPM_UNUSED_PATCH

  × installing dependencies
  ╰─▶ The following patches were not used: @sentry/junior@0.257.0, @sentry/
      junior-plugin-api@0.257.0
  help: Either remove them from "patchedDependencies" or update them to match
        packages in your dependencies.


@coderabbitai

coderabbitai Bot commented Oct 27, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: cbfb761e-9951-4f79-a5b9-5691eb5326bb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch 3 times, most recently from 12a37b8 to c5963d6 Compare October 28, 2026 20:45
@renovate renovate Bot changed the title Update junior monorepo to v0.258.0 Update junior monorepo to v0.259.0 Oct 28, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch from c5963d6 to ce5918d Compare October 29, 2026 07:15
@renovate renovate Bot changed the title Update junior monorepo to v0.259.0 Update junior monorepo to v0.260.0 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch from ce5918d to d81dd26 Compare October 29, 2026 18:26
@renovate renovate Bot changed the title Update junior monorepo to v0.260.0 Update junior monorepo to v0.261.0 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch from d81dd26 to d3354b2 Compare October 29, 2026 21:20
@renovate renovate Bot changed the title Update junior monorepo to v0.261.0 Update junior monorepo to v0.262.0 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch from d3354b2 to aad43f0 Compare October 30, 2026 02:00
@renovate renovate Bot changed the title Update junior monorepo to v0.262.0 Update junior monorepo to v0.263.0 Oct 30, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch 2 times, most recently from ef1f7b0 to f5499d2 Compare October 30, 2026 05:29
@renovate renovate Bot changed the title Update junior monorepo to v0.263.0 Update junior monorepo to v0.264.0 Oct 30, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch 2 times, most recently from 9bc796b to 47a6ec7 Compare October 31, 2026 01:41
@renovate renovate Bot changed the title Update junior monorepo to v0.264.0 Update junior monorepo to v0.265.0 Oct 31, 2026
@renovate
renovate Bot force-pushed the renovate/junior-monorepo branch from 47a6ec7 to 7db9b5d Compare October 31, 2026 05:49
@renovate renovate Bot changed the title Update junior monorepo to v0.265.0 Update junior monorepo to v0.266.0 Oct 31, 2026
@jonahsnider
jonahsnider marked this pull request as draft October 31, 2026 19:08
auto-merge was automatically disabled October 31, 2026 19:08

Pull request was converted to draft

@jonahsnider

jonahsnider commented Oct 31, 2026 •

Copy link
Copy Markdown
Member

Junior 0.257.0 → 0.266.0 review: keep this PR draft; do not merge yet. I converted it to draft, and GitHub reports autoMergeRequest: null.

Pushed validated fixes to the existing renovate/junior-monorepo branch in 933feb6, then integrated main's intervening Slack socket-mode update in e4e5638 to clear the dependency conflict. GitHub verifies both commits' signatures. The PR now has no conflicts. The Slack/Dashboard policy follows the maintainer's clarification: Slack stays open to everyone in the workspace, Dashboard stays restricted to team581.com.

  • Rebased both pnpm patches onto the published 0.266.0 artifacts (agent-runner-BtYK7bht.js, client-B0YZfxNy.js, and plugin API declarations), updated patchedDependencies, and regenerated pnpm-lock.yaml. Preserved the mcpAccessToken hook and the Kimi K3.1 Pro gateway override. Added one focused dist/app.js hunk that keeps Slack open to every verified workspace member while retaining the Dashboard domain allowlist.
  • Updated the version-sensitive gateway test to the current bundle and resolver export (s, previously o).
  • Fixed a startup-breaking config change: removed dashboard.allowedGoogleDomains from runtime/Nitro config and moved team581.com to createApp({ allowedDomains }).
  • Adopted Junior's new withSentryConfig export from @sentry/junior/nitro and removed Bolt's separate @sentry/nitro pin. Junior now owns aligned Sentry runtime/build SDK versions and the matching release name.
  • Per the maintainer's clarification, separated access policy in the runtime patch: Slack has no email-domain restriction; Dashboard stays restricted to team581.com. No extra Slack scope or app reinstall is needed for this policy. Documented the patch and legacy environment-variable cleanup.

Validation passed on Node 26.12.1 / pnpm 12.16.1:

  • vp install --frozen-lockfile
  • vp check (format, lint, types)
  • vp test: 6 files, 60 tests
  • vp run check:junior: all seven custom plugins load; configuration/content validation passes
  • vp run build: Nitro/Vercel build succeeds; output contains both custom patched behaviors
  • Bolt app startup and unauthenticated route checks with CI placeholder credentials: / redirects to /auth/login, /auth/login redirects to Google's authorization endpoint, /api/config returns 401. The OAuth redirect was not followed.
  • Focused observation/execution of the installed app confirms Slack's domain gate accepts personal-email profiles, Dashboard accepts team581.com Workspace claims but rejects other/missing hosted-domain claims, Google OAuth redirects with hd=team581.com, unauthenticated APIs return 401, and unsigned Slack webhooks return 401.
  • Focused smoke execution of the installed MCP orchestration: the hook wins over JWT/personal OAuth without an actor/session, supplies refreshed bearer tokens, propagates token failures, and does not enter interactive auth.

Reviewed CHANGELOG 0.258.0–0.266.0. Relevant findings:

  1. Separate Slack/Dashboard policy implemented (0.258 / 0.261 / 0.266): upstream now shares one domain list between Slack and Dashboard, but the maintainer confirmed that Slack must remain available to everyone in the workspace while Dashboard is more restricted. The custom runtime patch passes an empty domain list only to Slack webhook services; createApp({ allowedDomains: ["team581.com"] }) still gates Dashboard Google sign-in and authenticated APIs. Slack webhook signatures and workspace-membership checks are unchanged. users:read.email and bot domain exemptions are not needed with this policy. Unset JUNIOR_DASHBOARD_GOOGLE_DOMAINS if configured: that legacy variable now makes startup fail. Direct Google ID-token sign-in is disabled; use the browser OAuth flow.
  2. New built-in plugins: read-only PagerDuty in 0.258 and Figma in 0.263. Neither replaces Bolt's Google Groups/student membership, GitHub student membership, read-only Workspace MCP integrations, or sandbox preparation. They were not registered/enabled by this change.
  3. Service accounts (0.259): upstream plugin service accounts use an admin OAuth sign-in and stored grant. They do not replace Bolt's Google service-account key → short-lived read-only access-token hook, so both patches remain necessary. Plugin-context caching (0.262), redirect-vs-deny tool blocking (0.263), and the newest-waiting-request auth resume fix (0.266) are relevant integration behavior changes; current custom registrations/type checks/tests pass.
  4. Slack/automations/events: passive replies now use a decision model (0.259); event automations default to 10 runs/minute with a configurable window (0.258); event batches become one task message (0.260); stricter filter validation (0.265) and trusted/scope event-data changes (0.266) can change existing automation matching. Verify active automations after upgrade. Bolt does not register Junior's GitHub/Vercel/Sentry provider plugins, so their new event/PR behavior is not automatically enabled here.
  5. Runtime: child-agent delegation and plugin binary PATH precedence changed in 0.262; sandbox provider/trace handling changed in 0.265. Run a real sandbox preparation + delegated-task smoke check before rollout. S3-compatible attachment storage is optional in 0.265; Bolt's Blob setup was retained. Sentry v11 and the new Nitro wrapper are covered by the dependency/import migration and successful build, but production trace/source-map delivery still needs verification.

Remaining vetting: exercise live Google login, one read-only Workspace MCP request, Slack mention/passive reply, existing automations, attachment/queue/storage, and a real sandbox run in a configured preview. Local checks used placeholders and did not exercise production credentials or infrastructure. GitHub checks passed on e4e5638: Build + Fallow, push Autofix, and PR Autofix. All local checks were also rerun successfully after integrating main. CodeRabbit skipped review. Vercel reported success because the Ignored Build Step skipped its preview deployment; there is no new live preview from this run. No merge was performed.

@renovate

renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@jonahsnider
jonahsnider marked this pull request as ready for review October 31, 2026 22:12
@jonahsnider
jonahsnider merged commit d5c7f0b into main Oct 31, 2026
6 checks passed
@jonahsnider
jonahsnider deleted the renovate/junior-monorepo branch October 31, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant