Merge branch 'main' into leoortizz_nextjsproxyfixes

Author: leoortizz

.github/workflows/jules_bot_action.yml

@@ -29,6 +29,9 @@ jobs:
           JULES_KEY: ${{ secrets.JULES_KEY }}
           GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }}
           GOOGLE_API_KEY: ${{ secrets.GEMINI_API_KEY }}
+          ISSUE_TITLE: ${{ github.event.issue.title }}
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          ISSUE_BODY: ${{ github.event.issue.body }}
+          ISSUE_URL: ${{ github.event.issue.html_url }}
         run: |
-          printf -v PROMPT "%q\n" "Triage this new issue: ${{ github.event.issue.title }} ${{ github.event.issue.number }} ${{ github.event.issue.body }} ${{ github.event.issue.html_url }}"
-          python julesbot/issues_call.py --prompt "$PROMPT"
+          python julesbot/issues_call.py --prompt "Triage this new issue: $ISSUE_TITLE $ISSUE_NUMBER $ISSUE_BODY $ISSUE_URL"

CHANGELOG.md

@@ -1,2 +1 @@
-- Update Data Connect Emulator to 3.0.1, which addresses some internal errors (#9627)
 - Fix proxy.js/proxy.ts in Next.js 16 (#9631)

julesbot/issue_to_jules_agent/agent.py

@@ -72,6 +72,8 @@ def jules_create_session(prompt: str, title: str) -> dict:
             "source": "sources/github/firebase/firebase-tools",
             "githubRepoContext": {"startingBranch": "main"},
         },
+        "requirePlanApproval": False,
+        "automationMode": "AUTO_CREATE_PR",
         "title": title,
     }
 
@@ -115,25 +117,23 @@ def jules_create_session(prompt: str, title: str) -> dict:
 5.  **Add Commit Instructions:** Always include the standard "Commit & PR Instructions" as shown in the example, using the provided `issue_number`.
 
 ### Input Placeholders
-- `{{issue_body}}`: The raw text of the issue report.
-- `{{discussion_body}}`: (Optional) The raw text of the discussion.
-- `{{original_link}}`: The URL to the original issue.
-- `{{issue_number}}`: The numerical ID of the issue.
-- `{{reproduction_steps}}`: (Optional) Pre-written steps to reproduce the issue.
+- `<issue_body>`: The raw text of the issue report.
+- `<discussion_body>`: (Optional) The raw text of the discussion.
+- `<original_link>`: The URL to the original issue.
+- `<issue_number>`: The numerical ID of the issue.
+- `<reproduction_steps>`: (Optional) Pre-written steps to reproduce the issue.
 
 ### Output Template & Example
 
 ---
 
 #### Example Input:
 ```json
-{
   "issue_body": "The login button looks weird on my phone. It's all the way on the right and hard to click. I'm using Safari.",
   "discussion_body": "User @dev1 confirmed this on iOS 15. It looks like a flexbox alignment problem in `container.css`. Should be a quick fix.",
   "original_link": "https://github.com/example/project/issues/123",
   "issue_number": "123",
   "reproduction_steps": ""
-}
 ```
 
 #### Corresponding Desired Output:
@@ -170,10 +170,11 @@ def jules_create_session(prompt: str, title: str) -> dict:
     Your job is to triage a GitHub issue. The tasks you should perform are:
     1. Determine if an issue is spam using the is_spam agent. If it is spam, use the issue_write tool to update the issue state to "closed" and then you are done.
     2. If it is not spam, hand off the issue to the LABELER tool (labeler_agent). When the LABELER tool is done, use the issue_write tool to update the issue with the suggested labels and add a label called 'Triaged by JulesBot'.
-    3. Use the issue_type_agent to determine the type of issue. If it is a support request or feature request, report back and you are done.
+    3. Use the issue_type_agent to determine the type of issue.
     4. If you have not done so yet, use the issue_read tool to get the comments on the issue, to help inform the next steps
-    5. If it is a bug, use the complexity_scoping_agent to determine the complexity of the issue.
-    6. If it is a bug with complexity of less than 30, use the jules_agent to submit it to Jules.
+    5. If it is a support request, write up a reply. Maintain a helpful tone and try to debug the issue for the user. **DO NOT** actually send this reply, just report it back and you are done.
+    6. If it is a feature request or bug, use the complexity_scoping_agent to determine the complexity of the issue.
+    7. If it has a complexity of less than 40, use the jules_agent to submit it to Jules, and then you are done. If it has a complexity of 40 or more, report back the reasoning for the complexity score and you are done.
     """,
     tools=[github_toolset, IS_SPAM, ISSUE_TYPE, COMPLEXITY_SCORE, LABELER],
     sub_agents=[jules_agent],

npm-shrinkwrap.json

@@ -1,6 +1,6 @@
 {
   "name": "firebase-tools",
-  "version": "15.0.0",
+  "version": "15.1.0",
   "description": "Command-Line Interface for Firebase",
   "main": "./lib/index.js",
   "mcpName": "io.github.firebase/firebase-mcp",

package.json

@@ -61,7 +61,7 @@ export function instanceConsoleLink(projectId: string, instanceId: string) {
 }
 
 export type DataConnectLabel = "ft" | "nt";
-export const DEFAULT_DATABASE_VERSION = "POSTGRES_15";
+export const DEFAULT_DATABASE_VERSION = "POSTGRES_17";
 
 export async function createInstance(args: {
   projectId: string;

src/gcp/cloudsql/cloudsqladmin.ts

@@ -287,7 +287,7 @@ const throttlerTest = (ThrottlerConstructor: ThrottlerConstructorType): void =>
     expect(err.message).to.equal("Task index 0 failed: timed out after 100ms.");
   });
 
-  it("should reject with RetriesExhaustedError if last trial is rejected before timeout", async () => {
+  it.skip("should reject with RetriesExhaustedError if last trial is rejected before timeout", async () => {
     const handler = sinon.stub().rejects(TEST_ERROR);
 
     const q = new Queue({
@@ -336,7 +336,6 @@ const throttlerTest = (ThrottlerConstructor: ThrottlerConstructorType): void =>
     expect(q.complete).to.equal(1);
     expect(q.success).to.equal(0);
     expect(q.errored).to.equal(1);
-    expect(q.retried).to.be.at.least(2);
     expect(q.total).to.equal(1);
   });