feat: add automations module

[kewynakshlley]

No description provided.

[cubic-dev-ai]

7 issues found across 27 files

Confidence score: 2/5

• There is a concrete runtime regression risk in the builder APIs: CreateAutomationOptions and UpdateAutomationOptions use Arrays.asList in steps(...)/edges(...), so later step(...)/edge(...) calls can throw UnsupportedOperationException in normal chaining flows.
• src/test/java/com/resend/services/automations/AutomationsTest.java currently mocks the class under test, which weakens verification of real Automations behavior and makes the above regressions more likely to slip through.
• src/main/java/com/resend/Resend.java introduces Automations service wiring, and API-key permission requirements for Automations are still a deployment risk if production keys are not aligned.
• Pay close attention to src/main/java/com/resend/services/automations/model/CreateAutomationOptions.java, src/main/java/com/resend/services/automations/model/UpdateAutomationOptions.java, and src/test/java/com/resend/services/automations/AutomationsTest.java - mutable list safety in builders and real behavior test coverage need fixes before merge.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/main/java/com/resend/services/automations/model/UpdateAutomationOptions.java">

<violation number="1" location="src/main/java/com/resend/services/automations/model/UpdateAutomationOptions.java:92">
P2: `steps(...)` stores a fixed-size list. If a caller later uses `step(...)`, it will throw UnsupportedOperationException. Wrap the varargs in a mutable list to keep the builder API safe.</violation>

<violation number="2" location="src/main/java/com/resend/services/automations/model/UpdateAutomationOptions.java:110">
P2: `edges(...)` stores a fixed-size list. If a caller later uses `edge(...)`, it will throw UnsupportedOperationException. Wrap the varargs in a mutable list to keep the builder API safe.</violation>
</file>

<file name="src/main/java/com/resend/services/automations/model/CreateAutomationOptions.java">

<violation number="1" location="src/main/java/com/resend/services/automations/model/CreateAutomationOptions.java:74">
P1: Using `Arrays.asList` in `steps(...)` creates a fixed-size list that breaks subsequent `step(...)` calls with `UnsupportedOperationException`.</violation>

<violation number="2" location="src/main/java/com/resend/services/automations/model/CreateAutomationOptions.java:89">
P1: Using `Arrays.asList` in `edges(...)` creates a fixed-size list that breaks subsequent `edge(...)` calls with `UnsupportedOperationException`.</violation>
</file>

<file name="src/test/java/com/resend/services/automations/AutomationsTest.java">

<violation number="1" location="src/test/java/com/resend/services/automations/AutomationsTest.java:22">
P1: These tests mock the class under test, so they only verify Mockito stubbing instead of real Automations behavior.</violation>
</file>

<file name="src/main/java/com/resend/services/automations/Automations.java">

<violation number="1" location="src/main/java/com/resend/services/automations/Automations.java:165">
P2: `buildQueryString` and `buildRunsQueryString` duplicate the same query assembly logic; consolidate to one shared helper to prevent drift.</violation>
</file>

<file name="src/main/java/com/resend/Resend.java">

<violation number="1" location="src/main/java/com/resend/Resend.java:171">
P1: Custom agent: **API Key Permission Check SDK Methods**

This adds the Automations service to the SDK. Please confirm that production API keys have the required permissions for Automations operations to prevent permission-related failures after deployment.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

1 issue found across 3 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/main/java/com/resend/services/automations/model/GetAutomationRunOptions.java">

<violation number="1" location="src/main/java/com/resend/services/automations/model/GetAutomationRunOptions.java:58">
P2: Validate `automationId` and `runId` in `build()` before creating the options to prevent malformed run lookup URLs.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[cubic-dev-ai]

3 issues found across 3 files (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/main/java/com/resend/services/automations/model/ListAutomationsParams.java">

<violation number="1" location="src/main/java/com/resend/services/automations/model/ListAutomationsParams.java:86">
P1: Query parameters are serialized without URL encoding, which can break pagination/status values containing reserved characters.</violation>
</file>

<file name="src/main/java/com/resend/services/automations/model/ListAutomationRunsParams.java">

<violation number="1" location="src/main/java/com/resend/services/automations/model/ListAutomationRunsParams.java:86">
P2: Query parameters are concatenated without URL encoding, which can break pagination/status requests when values contain reserved URL characters.</violation>
</file>

<file name="src/main/java/com/resend/services/automations/Automations.java">

<violation number="1" location="src/main/java/com/resend/services/automations/Automations.java:87">
P1: Possible NullPointerException: `params` is dereferenced without a null check when building the query string.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}

[zenorocha]

@cursor resolve conflicts

[cursor]

• I merged main into feat/automations and resolved the only conflict in src/main/java/com/resend/Resend.java by keeping both events() and automations() service accessors.
• Committed and pushed the resolution to feat/automations (latest commit: Resolve merge conflict in Resend.java: keep both events() and automations() services). The PR now shows as mergeable; any remaining “blocked” state is from checks, not conflicts.

Note: I couldn’t run the build locally because the repo uses Gradle 7.4, which isn’t compatible with JDK 21 on this VM. If you want me to run tests here, either switch the VM to JDK 17 or upgrade the Gradle wrapper to a Java 21–compatible version (e.g., 8.6+).