Skip to content

feat(nextjs): Include metadata as headers on keyless creation #6483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

heatlikeheatwave
Copy link
Contributor

@heatlikeheatwave heatlikeheatwave commented Aug 6, 2025

Description

To help us debug why keyless applications are failing to make API requests, this PR forwards the user-agent, arch, platform, nextjs version, and npm config with POST requests to create keyless app instance.

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

Summary by CodeRabbit

  • New Features

    • Enhanced telemetry and environment metadata collection during accountless application onboarding and creation.
    • Automatic inclusion of runtime and request metadata as HTTP headers for improved tracking and analytics.
    • Added ability to forward additional HTTP headers with accountless application requests.
  • Bug Fixes

    • Improved error handling to ensure silent failure if metadata collection encounters issues, preventing user-facing disruptions.

Copy link

changeset-bot bot commented Aug 6, 2025

🦋 Changeset detected

Latest commit: e8cc210

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages
Name Type
@clerk/backend Patch
@clerk/nextjs Patch
@clerk/agent-toolkit Patch
@clerk/astro Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/remix Patch
@clerk/tanstack-react-start Patch
@clerk/testing Patch

Not sure what this means? Click here to learn what changesets are.

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

Copy link

vercel bot commented Aug 6, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 7, 2025 8:17pm

@heatlikeheatwave heatlikeheatwave changed the title feat(nextjs): Forward user-agent, arch, platform, and npm config with POST requests to create keyless app instance feat(nextjs): Forward user-agent, arch, platform, next.js version and npm config with POST requests to create keyless app instance Aug 6, 2025
Copy link

pkg-pr-new bot commented Aug 6, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6483

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6483

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6483

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6483

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6483

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6483

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6483

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6483

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6483

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6483

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6483

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6483

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6483

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6483

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6483

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6483

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6483

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6483

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6483

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6483

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6483

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6483

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6483

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6483

commit: e8cc210

Copy link
Contributor

coderabbitai bot commented Aug 6, 2025

📝 Walkthrough

Walkthrough

The changes implement telemetry and metadata forwarding enhancements for accountless application workflows. Backend API methods for creating and completing accountless applications now accept an optional Headers parameter, which is converted into plain objects and passed as request options. On the Next.js side, a new module collects runtime and request metadata—such as Node.js version, Next.js version, npm user-agent, and client user-agent—and formats it into HTTP headers. These headers are asynchronously gathered and passed into the backend API calls for creating and completing accountless applications, with error handling to default to empty headers if collection fails. The update also includes a patch to forward user-agent, architecture, platform, and npm configuration details with POST requests to the /accountless_applications endpoint.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~15–20 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b8775e8 and 08d30b0.

📒 Files selected for processing (5)
  • .changeset/strong-chicken-lie.md (1 hunks)
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts (1 hunks)
  • packages/nextjs/src/app-router/server/keyless-provider.tsx (2 hunks)
  • packages/nextjs/src/server/keyless-custom-headers.ts (1 hunks)
  • packages/nextjs/src/server/keyless-node.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (5)
  • .changeset/strong-chicken-lie.md
  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)
  • GitHub Check: Integration Tests (nextjs, chrome, 14)
  • GitHub Check: Integration Tests (react-router, chrome)
  • GitHub Check: Integration Tests (nextjs, chrome, 15)
  • GitHub Check: Integration Tests (billing, chrome)
  • GitHub Check: Integration Tests (nuxt, chrome)
  • GitHub Check: Integration Tests (vue, chrome)
  • GitHub Check: Integration Tests (quickstart, chrome)
  • GitHub Check: Integration Tests (tanstack-react-router, chrome)
  • GitHub Check: Integration Tests (tanstack-react-start, chrome)
  • GitHub Check: Integration Tests (sessions, chrome)
  • GitHub Check: Integration Tests (astro, chrome)
  • GitHub Check: Integration Tests (express, chrome)
  • GitHub Check: Integration Tests (expo-web, chrome)
  • GitHub Check: Integration Tests (localhost, chrome)
  • GitHub Check: Integration Tests (generic, chrome)
  • GitHub Check: Integration Tests (ap-flows, chrome)
  • GitHub Check: Integration Tests (elements, chrome)
  • GitHub Check: Unit Tests (22, **)
  • GitHub Check: Publish with pkg-pr-new
  • GitHub Check: Unit Tests (18, --filter=@clerk/astro --filter=@clerk/backend --filter=@clerk/express --filter=@c...
  • GitHub Check: Static analysis
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts (1)

27-29: Track the TODO for abandon functionality.

The placeholder method is appropriate for this PR, but ensure the abandon functionality is tracked in your issue management system.

Would you like me to create a GitHub issue to track the implementation of the abandonAccountlessApplication functionality?

packages/nextjs/src/server/keyless-custom-headers.ts (1)

25-32: Consider improving Next.js version extraction robustness.

The regex parsing of process.title is clever but could be fragile if the format changes. The current implementation might return the entire process.title as fallback which could contain sensitive information.

Consider this more defensive approach:

   nextVersion: () => {
     try {
       // Extract version from process.title: 'next-server (v15.4.5)' -> 'v15.4.5'
       const match = process.title.match(/\(v([\d.]+)\)/);
-      return match ? `v${match[1]}` : process.title;
+      return match ? `v${match[1]}` : undefined;
     } catch {
       return undefined;
     }
   },
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ad16da and bab2a80.

📒 Files selected for processing (4)
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts (1 hunks)
  • packages/nextjs/src/app-router/server/keyless-provider.tsx (2 hunks)
  • packages/nextjs/src/server/keyless-custom-headers.ts (1 hunks)
  • packages/nextjs/src/server/keyless-node.ts (2 hunks)
🧰 Additional context used
📓 Path-based instructions (9)
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
packages/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

TypeScript is required for all packages

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
packages/**/*.{ts,tsx,d.ts}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Packages should export TypeScript types alongside runtime code

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use proper TypeScript error types

**/*.{ts,tsx}: Always define explicit return types for functions, especially public APIs
Use proper type annotations for variables and parameters where inference isn't clear
Avoid any type - prefer unknown when type is uncertain, then narrow with type guards
Use interface for object shapes that might be extended
Use type for unions, primitives, and computed types
Prefer readonly properties for immutable data structures
Use private for internal implementation details
Use protected for inheritance hierarchies
Use public explicitly for clarity in public APIs
Prefer readonly for properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Use const assertions for literal types: as const
Use satisfies operator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports: import type { ... } from ...
No any types without justification
Proper error handling with typed errors
Consistent use of readonly for immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
**/*.{js,ts,tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
**/*

⚙️ CodeRabbit Configuration File

If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Files:

  • packages/nextjs/src/server/keyless-node.ts
  • packages/nextjs/src/app-router/server/keyless-provider.tsx
  • packages/nextjs/src/server/keyless-custom-headers.ts
  • packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts
**/*.{jsx,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

**/*.{jsx,tsx}: Use error boundaries in React components
Minimize re-renders in React components

**/*.{jsx,tsx}: Always use functional components with hooks instead of class components
Follow PascalCase naming for components: UserProfile, NavigationMenu
Keep components focused on a single responsibility - split large components
Limit component size to 150-200 lines; extract logic into custom hooks
Use composition over inheritance - prefer smaller, composable components
Export components as named exports for better tree-shaking
One component per file with matching filename and component name
Use useState for simple state management
Use useReducer for complex state logic
Implement proper state initialization
Use proper state updates with callbacks
Implement proper state cleanup
Use Context API for theme/authentication
Implement proper state selectors
Use proper state normalization
Implement proper state persistence
Use React.memo for expensive components
Implement proper useCallback for handlers
Use proper useMemo for expensive computations
Implement proper virtualization for lists
Use proper code splitting with React.lazy
Implement proper cleanup in useEffect
Use proper refs for DOM access
Implement proper event listener cleanup
Use proper abort controllers for fetch
Implement proper subscription cleanup
Use proper HTML elements
Implement proper ARIA attributes
Use proper heading hierarchy
Implement proper form labels
Use proper button types
Implement proper focus management
Use proper keyboard shortcuts
Implement proper tab order
Use proper skip links
Implement proper focus traps
Implement proper error boundaries
Use proper error logging
Implement proper error recovery
Use proper error messages
Implement proper error fallbacks
Use proper form validation
Implement proper error states
Use proper error messages
Implement proper form submission
Use proper form reset
Use proper component naming
Implement proper file naming
Use proper prop naming
Implement proper...

Files:

  • packages/nextjs/src/app-router/server/keyless-provider.tsx
**/*.tsx

📄 CodeRabbit Inference Engine (.cursor/rules/react.mdc)

**/*.tsx: Use proper type definitions for props and state
Leverage TypeScript's type inference where possible
Use proper event types for handlers
Implement proper generic types for reusable components
Use proper type guards for conditional rendering

Files:

  • packages/nextjs/src/app-router/server/keyless-provider.tsx
🧬 Code Graph Analysis (2)
packages/nextjs/src/server/keyless-node.ts (1)
packages/nextjs/src/server/keyless-custom-headers.ts (2)
  • collectKeylessMetadata (52-64)
  • formatMetadataHeaders (69-80)
packages/nextjs/src/app-router/server/keyless-provider.tsx (2)
packages/nextjs/src/server/keyless-custom-headers.ts (2)
  • collectKeylessMetadata (52-64)
  • formatMetadataHeaders (69-80)
packages/nextjs/src/server/keyless-log-cache.ts (1)
  • clerkDevelopmentCache (64-64)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)
  • GitHub Check: Build Packages
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (12)
packages/nextjs/src/app-router/server/keyless-provider.tsx (2)

8-8: LGTM!

The import statement correctly brings in the telemetry collection functions needed for the keyless metadata feature.


110-110: API call correctly forwards telemetry headers.

The modification properly passes the collected metadata headers to the backend API, aligning with the updated method signature.

packages/nextjs/src/server/keyless-node.ts (2)

5-5: LGTM!

The import statement correctly brings in the required telemetry collection functions.


149-149: LGTM!

The API call correctly passes the collected telemetry headers to the backend method.

packages/backend/src/api/endpoints/AccountlessApplicationsAPI.ts (3)

8-8: LGTM!

The method signatures correctly accept optional Headers parameters while maintaining backward compatibility through the optional type.

Also applies to: 17-17


9-9: LGTM!

The header conversion logic properly transforms Headers objects to plain objects using the standard approach with type guards for safety.

Also applies to: 18-18


13-13: LGTM!

The headerParams correctly forwards the converted telemetry headers through the request system.

Also applies to: 23-23

packages/nextjs/src/server/keyless-custom-headers.ts (5)

3-8: LGTM!

The interface is well-designed with appropriate optional properties and clear naming conventions for telemetry metadata.


13-18: LGTM!

The header mapping properly namespaces headers with 'Clerk-' prefix and follows HTTP header conventions. The 'as const' assertion ensures type safety.


41-47: LGTM!

The safeCollect utility function provides robust error handling for metadata collection with proper generic typing.


52-64: LGTM!

The function efficiently collects metadata using concurrent execution with Promise.all and properly combines environment and request data.


69-80: LGTM!

The function efficiently converts metadata to HTTP headers with proper filtering and type-safe mapping using the centralized header configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
.changeset/strong-chicken-lie.md (1)

6-6: Update summary to reflect all forwarded metadata

The implementation also forwards the Next.js version, but the changeset text omits it. Including every forwarded field avoids confusion when reading the changelog.

-feat(nextjs): Forward user-agent, arch, platform, and npm config with POST requests to /accountless_applications
+feat(nextjs): Forward user-agent, arch, platform, next.js version, and npm config with POST requests to /accountless_applications
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bab2a80 and 946db15.

📒 Files selected for processing (1)
  • .changeset/strong-chicken-lie.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
.changeset/**

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Automated releases must use Changesets.

Files:

  • .changeset/strong-chicken-lie.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan

@heatlikeheatwave heatlikeheatwave force-pushed the heat/grow-664-investigate-10-drop-between-application-created-and-dev branch from 946db15 to 76eb474 Compare August 7, 2025 14:00
Copy link
Member

@nikosdouvlis nikosdouvlis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@heatlikeheatwave great job! I've left a few minor comments, approving to unblock for when everything's ready

@panteliselef panteliselef changed the title feat(nextjs): Forward user-agent, arch, platform, next.js version and npm config with POST requests to create keyless app instance feat(nextjs): Include metadata as headers on keyless creation Aug 7, 2025
@heatlikeheatwave heatlikeheatwave force-pushed the heat/grow-664-investigate-10-drop-between-application-created-and-dev branch 2 times, most recently from 2929090 to 9dbf813 Compare August 7, 2025 16:53
@heatlikeheatwave heatlikeheatwave enabled auto-merge (squash) August 7, 2025 17:26
@heatlikeheatwave heatlikeheatwave force-pushed the heat/grow-664-investigate-10-drop-between-application-created-and-dev branch from 1332fb3 to b8775e8 Compare August 7, 2025 17:44
@heatlikeheatwave heatlikeheatwave enabled auto-merge (squash) August 7, 2025 19:03
@heatlikeheatwave heatlikeheatwave force-pushed the heat/grow-664-investigate-10-drop-between-application-created-and-dev branch from d6462c1 to 08d30b0 Compare August 7, 2025 19:05
@heatlikeheatwave heatlikeheatwave merged commit 0d27281 into main Aug 7, 2025
36 checks passed
@heatlikeheatwave heatlikeheatwave deleted the heat/grow-664-investigate-10-drop-between-application-created-and-dev branch August 7, 2025 20:30
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.

6 participants