Exclude @inkeep/* packages from minimum release age by amikofalvy · Pull Request #2968 · inkeep/agents

amikofalvy · 2026-04-02T03:09:41Z

Summary

Updated the pnpm workspace configuration to exclude @inkeep/* scoped packages from the minimum release age requirement.

Changes

Added minimumReleaseAgeExclude configuration to the workspace manifest
Configured the exclusion to apply to all packages under the @inkeep/* scope

Details

This change allows @inkeep/* packages to be released without waiting for the standard 1440-minute (24-hour) minimum release age, while other packages continue to follow the existing release age policy. This provides more flexibility for releasing internal or frequently-updated packages within the Inkeep scope.

https://claude.ai/code/session_01LBEnpfsjj6r4cdwXs2VeHx

Excludes @inkeep scoped packages from the 1440-minute minimum release age gate so our own published packages can be installed immediately after release. https://claude.ai/code/session_01LBEnpfsjj6r4cdwXs2VeHx

changeset-bot · 2026-04-02T03:09:47Z

⚠️ No Changeset found

Latest commit: 0f08ed9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

vercel · 2026-04-02T03:09:47Z

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

Project	Deployment	Actions	Updated (UTC)
agents-api	Ready	Preview, Comment	Apr 2, 2026 3:09am
agents-docs	Ready	Preview, Comment	Apr 2, 2026 3:09am
agents-manage-ui	Ready	Preview, Comment	Apr 2, 2026 3:09am

pullfrog · 2026-04-02T03:10:57Z

TL;DR — Exempts all @inkeep/* scoped packages from pnpm's 24-hour minimum release age gate, allowing faster publishes for first-party packages while keeping the safeguard for third-party dependencies.

Key changes

Exclude @inkeep/* from minimumReleaseAge — Adds minimumReleaseAgeExclude to the workspace manifest so first-party packages bypass the 1440-minute cooldown that still applies to everything else.

_{Summary ｜ 1 file ｜ 1 commit ｜ base: main ← claude/add-minimum-release-age-exclude-UQn2M}

Before: All packages — including @inkeep/* — were subject to a 1440-minute minimum release age, blocking rapid iteration on first-party packages.
After: @inkeep/* packages are excluded via minimumReleaseAgeExclude, enabling immediate publishes while third-party dependencies retain the cooldown.

The minimumReleaseAge setting tells pnpm to reject resolved versions published less than 24 hours ago — a supply-chain hardening measure against typosquatting and compromised publishes. Since @inkeep/* packages are owned by this organization, the delay adds friction without meaningful security benefit.

pnpm-workspace.yaml

^{｜ View workflow run ｜ Triggered by Pullfrog ｜ Using Claude Opus ｜ 𝕏}

pullfrog

Clean, low-risk change. minimumReleaseAgeExclude is a documented pnpm setting (v10.17.0+ for pattern support), and the repo runs pnpm 10.33.0. Exempting @inkeep/* from the 24-hour minimum release age is reasonable — this supply-chain protection targets third-party dependencies, not your own published packages.

^{｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

claude

PR Review Summary

(0) Total Issues | Risk: Low

This PR adds a minimumReleaseAgeExclude configuration to allow @inkeep/* packages to bypass the 24-hour minimum release age requirement that applies to external dependencies.

Analysis

What the change does:

The existing minimumReleaseAge: 1440 setting requires all dependencies to have been published for at least 24 hours (1440 minutes) before pnpm will install them
The new minimumReleaseAgeExclude array exempts @inkeep/* scoped packages from this restriction
This affects all 12 internal packages: agents-api, agents-cli, agents-core, agents-docs, agents-manage-ui, agents-mcp, agents-sdk, agents-ui-demo, agents-work-apps, agents-email, ai-sdk-provider, and create-agents

Why this makes sense:

The minimum release age policy is a supply-chain security measure to delay installing potentially malicious packages until they've been public for 24 hours
First-party @inkeep/* packages don't need this protection — they're published by the organization itself
Exempting internal packages allows faster iteration and deployment cycles without waiting 24 hours after each publish

Configuration correctness:

The YAML syntax is correct — minimumReleaseAgeExclude is placed at the same level as minimumReleaseAge
The glob pattern '@inkeep/*' correctly matches all packages in the @inkeep scope
This is a documented pnpm feature that works with pnpm v10+

No Issues Found

This is a clean, well-scoped infrastructure change. No concerns identified.

✅ APPROVE

Summary: Simple, low-risk configuration addition that appropriately excludes first-party packages from a supply-chain security policy intended for third-party dependencies. LGTM! 🚀

github-actions · 2026-04-02T03:18:22Z

Preview URLs

Use these stable preview aliases for testing this PR:

UI: https://pr-2968-ui.preview.inkeep.com
API: https://pr-2968-api.preview.inkeep.com
API health: https://pr-2968-api.preview.inkeep.com/health

These point to the same Vercel preview deployment as the bot comment, but they stay stable and easier to find.

Raw Vercel deployment URLs

UI deployment: https://agents-manage-k286rdhl8.preview.inkeep.com
API deployment: https://agents-nied31vmr.preview.inkeep.com

Excludes @inkeep scoped packages from the 1440-minute minimum release age gate so our own published packages can be installed immediately after release. https://claude.ai/code/session_01LBEnpfsjj6r4cdwXs2VeHx Co-authored-by: Claude <[email protected]>

@claude

* chore(dashboard): dockerize visual regression tests for cross-OS consistency Run Playwright browser inside a Docker container so visual screenshot tests produce identical results on macOS (local dev) and Linux (CI). - Add docker-compose.visual.yml with Playwright server container - Update vitest config to connect to Docker browser via websocket when PW_TEST_CONNECT_WS_ENDPOINT env var is set - Add test:visual and test:visual:update npm scripts - Update CI workflow to use Docker Playwright server instead of bare Playwright install - Regenerate screenshot baselines from Linux container Closes PRD-6191 Co-Authored-By: Claude Opus 4.6 <[email protected]> * fix: address PR review feedback - Add explicit failure handling if Playwright server doesn't start - Bind Docker port to 127.0.0.1 only (don't expose to network) - Align npx playwright version with Docker image (both 1.58.0) Co-Authored-By: Claude Opus 4.6 <[email protected]> * fix: restore Playwright install step in CI The @vitest/browser-playwright package requires a local Playwright install to initialize, even when the actual browser runs in Docker via connectOptions. Keep the install step alongside the Docker server. Co-Authored-By: Claude Opus 4.6 <[email protected]> * fix(dashboard): pass PW_TEST_CONNECT_WS_ENDPOINT through turbo strict mode Turbo v2 strict mode filters env vars not listed in turbo.json from child processes. The Playwright WebSocket endpoint was being silently dropped, causing vitest to fall back to local Chromium instead of the Docker server — producing mismatched screenshots in CI. Also pins docker-compose.visual.yml to linux/amd64 so local baselines match CI regardless of host architecture (see microsoft/playwright#13873), and fixes the Playwright cache restore-keys prefix mismatch. Co-Authored-By: Claude Opus 4.6 <[email protected]> * docs: add visual regression test workflow to AGENTS.md * fix(dashboard): resolve Monaco strict locator violation in nested error state visual test * fix(dashboard): fix Monaco strict locator violation with data-testid and stable render wait * Refactor vitest.config.ts by removing unused code * Update vitest.config.ts * fix(dashboard): restore onUnhandledError handler for Monaco browser tests The previous refactor removed the onUnhandledError handler, causing CI to fail with exit code 1 due to 3 known, unfixable Monaco Editor errors in Vitest browser mode: 1. "Cannot use import statement outside a module" - Monaco web workers cannot load ESM in the Vitest browser sandbox 2. "InvalidCharacterError" / "is not a valid name" - Monaco attempts createElement with an SVG data URI as the tag name 3. "Closing rpc while" - Vitest worker RPC shutdown race condition These errors were originally suppressed by Nick in #2046 and #2078 after investigation confirmed they are unfixable Monaco/Vitest internals that do not affect test correctness. Refs: #2046, #2078 * fix(dashboard): remove unused pixelmatch devDependency The pixelmatch package is no longer imported after the vitest.config.ts refactor removed the custom tolerantPixelmatch comparator. Knip correctly flags it as unused. * fix * upd * upd * format * lock * rm * fix * Create fluffy-gorillas-joke.md * Apply suggestion from @claude[bot] Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> * fix(@inkeep/agents-work-apps): mark `@slack/socket-mode` as `dependency` (#2951) * upd * upd * Apply suggestion from @dimaMachina * Apply suggestion from @dimaMachina * Create breezy-lemons-dream.md * Document MCP header forwarding in Visual Builder docs (#2956) * docs: add MCP header forwarding and fix header key casing examples * updated warnings in headers docs * updated warnings in mcp servers docs * In product copilot tutorial (#2957) * docs build updated api reference * tutorial done * implements pnpm minimumReleaseAge and upgrades pnpm to 10.33.0 (#2958) * implements pnpm minimumReleaseAge * upgrades pnpm to 10.16.0 * upgrades pnpm to 10.33.0 * ci: surface stable preview URLs in PRs (#2799) * ci: surface stable preview urls in PRs * fix: add temp file cleanup trap and paginate comment search - Add EXIT trap to clean up mktemp file - Paginate through all PR comments when searching for the existing marker comment, fixing duplicate-comment risk on PRs with 100+ comments Co-authored-by: Andrew Mikofalvy <[email protected]> Co-Authored-By: Claude Opus 4.6 <[email protected]> * ci: fix preview URL comment updates --------- Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Andrew Mikofalvy <[email protected]> Co-authored-by: Claude Opus 4.6 <[email protected]> * feat: S3 presigned URLs for private media delivery (#2887) * feat: add S3 presigned URL support for private media delivery - Add optional getPresignedUrl() to BlobStorageProvider interface - Implement in S3BlobStorageProvider using @aws-sdk/s3-request-presigner - Make resolveMessageBlobUris() async with presigned URL first, manage proxy fallback for non-S3 backends (Option D hybrid) - Update both call sites (run + manage conversation routes) with await - Add presigned URL tests to s3-provider and resolve-blob-uris test suites - Include full spec with evidence files Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * docs: add S3 blob storage deployment guide Covers S3 setup, IAM permissions, env vars, S3-compatible services, storage backend priority, and presigned URL delivery flow. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * chore: add changeset for S3 presigned URL support Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * fix: add error handling for presigned URL failures with proxy fallback - Wrap getPresignedUrl() in try-catch so failures fall through to manage proxy URL instead of crashing the entire conversation response - Add test for presigned URL failure → proxy fallback path - Add mixed-content test with presigned URLs active - Fix doc icon quoting convention Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * fix: correct callout type and remove inaccurate configurable claim in docs Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * feat: make presigned URL expiry configurable via `BLOB_STORAGE_PRESIGNED_URL_EXPIRY_SECONDS` - Add `BLOB_STORAGE_PRESIGNED_URL_EXPIRY_SECONDS` to env.ts Zod schema (default 7200s / 2 hours, range 60–604800) - Replace hardcoded `DEFAULT_PRESIGNED_EXPIRY_SECONDS` constant in s3-provider.ts with env var lookup - Update tests to use env var in mocks and verify new default - Add env var to .env.example files and deployment docs * fix: address PR review comments - Clarify Vercel Blob is also a valid production backend (serves via proxy) - Add per-service S3-compatible path-style guidance (R2 vs B2 vs Spaces) - Make first resolve-blob-uris test explicitly set its mock (test isolation) Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * chore: reset lockfile from main to minimize resolution drift Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * fix: pin s3-request-presigner to match client-s3 to prevent lockfile drift Pin @aws-sdk/s3-request-presigner to 3.995.0 (same as resolved client-s3) to minimize pnpm-lock.yaml changes and prevent react version mismatch that caused agents-email test failures in CI. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * Resolve blob storage provider once per message list instead of per message Addresses PR feedback: call getBlobStorageProvider() once in resolveMessagesListBlobUris and pass the provider through to resolveMessageBlobUris, avoiding N singleton lookups per conversation retrieval. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * chore: reset lockfile from main and reinstall to fix CI Reset pnpm-lock.yaml from main per repo guidelines to prevent resolution drift that was causing monaco-editor ESM import failures in agents-manage-ui tests. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * Address remaining review suggestions: list-level presigned URL test and AWS CLI prerequisite - Add test for resolveMessagesListBlobUris with presigned URLs active across multiple messages, covering Promise.all handling - Add AWS CLI prerequisite note to S3 setup docs Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> * Remove AWS CLI prerequisite note from S3 docs Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]> --------- Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]> Co-authored-by: pullfrog[bot] <226033991+pullfrog[bot]@users.noreply.github.com> * ci: add preview janitor and recreate control (#2930) * ci: add preview state janitor and recreate path * ci: simplify preview janitor and var resolution * ci: address preview janitor review feedback * ci: gate preview auth on SpiceDB deployment readiness * ci: tighten preview bootstrap retry budget * ci: retry preview recreate after Railway delete * ci: clarify skipped preview workflow jobs * Rename headers in schema and usage to hyphen format (#2962) * Version Packages (#2952) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Andrew Mikofalvy <[email protected]> * Update actions/setup-node and pnpm/action-setup to Node.js 24 versions (#2963) Upgrade actions/setup-node from v4 to v6.3.0 and pnpm/action-setup from v4 to v5.0.0 across all workflows to resolve the Node.js 20 deprecation warning. Node.js 20 actions will be forced to Node.js 24 starting June 2, 2026. https://claude.ai/code/session_01D5Ah1eAYvZCS2SfZ5Lopi3 Co-authored-by: Claude <[email protected]> * credential id reference added (#2967) * Add minimumReleaseAgeExclude for @inkeep/* packages (#2968) Excludes @inkeep scoped packages from the 1440-minute minimum release age gate so our own published packages can be installed immediately after release. https://claude.ai/code/session_01LBEnpfsjj6r4cdwXs2VeHx Co-authored-by: Claude <[email protected]> * add TooltipProvider * add back timeout * should fix tests * polish * fix * pnpm i * upd --------- Co-authored-by: Varun Varahabhotla <[email protected]> Co-authored-by: Claude Opus 4.6 <[email protected]> Co-authored-by: Varun Varahabhotla <[email protected]> Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: bryan-inkeep <[email protected]> Co-authored-by: Gaurav Varma <[email protected]> Co-authored-by: robert-inkeep <[email protected]> Co-authored-by: claude[bot] <41898282+claude[bot]@users.noreply.github.com> Co-authored-by: Andrew Mikofalvy <[email protected]> Co-authored-by: Andrew Mikofalvy <[email protected]> Co-authored-by: pullfrog[bot] <226033991+pullfrog[bot]@users.noreply.github.com> Co-authored-by: inkeep-internal-ci[bot] <259778081+inkeep-internal-ci[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Add minimumReleaseAgeExclude for @inkeep/* packages

0f08ed9

Excludes @inkeep scoped packages from the 1440-minute minimum release age gate so our own published packages can be installed immediately after release. https://claude.ai/code/session_01LBEnpfsjj6r4cdwXs2VeHx

pullfrog Bot reviewed Apr 2, 2026

View reviewed changes

amikofalvy requested a review from robert-inkeep April 2, 2026 03:11

claude Bot reviewed Apr 2, 2026

View reviewed changes

github-actions Bot deleted a comment from claude Bot Apr 2, 2026

robert-inkeep enabled auto-merge April 2, 2026 03:12

robert-inkeep added this pull request to the merge queue Apr 2, 2026

Merged via the queue into main with commit 45fc0c4 Apr 2, 2026
28 checks passed

robert-inkeep deleted the claude/add-minimum-release-age-exclude-UQn2M branch April 2, 2026 03:30

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Exclude @inkeep/* packages from minimum release age#2968

Exclude @inkeep/* packages from minimum release age#2968
robert-inkeep merged 1 commit intomainfrom
claude/add-minimum-release-age-exclude-UQn2M

amikofalvy commented Apr 2, 2026

Uh oh!

changeset-bot Bot commented Apr 2, 2026

Uh oh!

vercel Bot commented Apr 2, 2026

Uh oh!

pullfrog Bot commented Apr 2, 2026

Uh oh!

pullfrog Bot left a comment

Uh oh!

claude Bot left a comment

Uh oh!

github-actions Bot commented Apr 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

amikofalvy commented Apr 2, 2026

Summary

Changes

Details

Uh oh!

changeset-bot Bot commented Apr 2, 2026

⚠️ No Changeset found

Uh oh!

vercel Bot commented Apr 2, 2026

Uh oh!

pullfrog Bot commented Apr 2, 2026

Key changes

Uh oh!

pullfrog Bot left a comment

Choose a reason for hiding this comment

Uh oh!

claude Bot left a comment

Choose a reason for hiding this comment

PR Review Summary

Analysis

No Issues Found

✅ APPROVE

Uh oh!

github-actions Bot commented Apr 2, 2026

Preview URLs

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants