Skip to content

chore: change app builder to bruno team#8218

Open
sid-bruno wants to merge 2 commits into
usebruno:mainfrom
sid-bruno:feat/migrate-team
Open

chore: change app builder to bruno team#8218
sid-bruno wants to merge 2 commits into
usebruno:mainfrom
sid-bruno:feat/migrate-team

Conversation

@sid-bruno

@sid-bruno sid-bruno commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Description

JIRA

Contribution Checklist:

  • I've used AI significantly to create this pull request
  • The pull request only addresses one issue or adds one feature.
  • The pull request does not introduce any breaking changes
  • I have added screenshots or gifs to help explain the change if applicable.
  • I have read the contribution guidelines.
  • Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

Publishing to New Package Managers

Please see here for more information.

Summary by CodeRabbit

  • Chores
    • Updated macOS signing identity and notarization configuration to use new organization credentials.
    • Notarization now specifies the notarization tool explicitly and includes the organization/team identifier.
    • Build logs updated to reference the resolved app bundle path after notarization.

Copilot AI review requested due to automatic review settings June 9, 2026 16:15
@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4b2fa113-5ef1-4983-9776-f80f816d945b

📥 Commits

Reviewing files that changed from the base of the PR and between 01c85ba and ecd9df3.

📒 Files selected for processing (1)
  • packages/bruno-electron/notarize.js
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/bruno-electron/notarize.js

Walkthrough

The PR switches macOS signing identity to Bruno Software, Inc. (P3WTZH48ZB) and updates the notarization script to pass tool: 'notarytool', use ascProvider = P3WTZH48ZB, include teamId, and log the resolved app bundle path.

Changes

macOS Signing and Notarization Credential Update

Layer / File(s) Summary
Build signing identity
packages/bruno-electron/electron-builder-config.js
Electron-builder mac.identity updated from Anoop MD (W7LPPWA48L) to Bruno Software, Inc. (P3WTZH48ZB).
Notarization credentials and tooling
packages/bruno-electron/notarize.js
Notarization call adds tool: 'notarytool', sets ascProvider and teamId to P3WTZH48ZB, and updates the completion log to print the resolved appPath.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

size/S

Suggested reviewers

  • helloanoop
  • lohit-bruno
  • naman-bruno
  • bijin-bruno

Poem

🍎 Signing keys traded, tidy and bright,
Notarytool steps in, beneath macOS light,
Bruno takes the helm with P3WTZH48ZB,
Builds sing, logs show paths, all neat as can be.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the macOS signing/notarization configuration from Anoop MD's identity to Bruno Software, Inc.'s team identity.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the macOS signing and notarization configuration for the Bruno Electron app to use the Bruno team/certificate, aligning the build pipeline with the new Apple developer team settings.

Changes:

  • Switch macOS code signing identity in the Electron Builder config to the Bruno Software, Inc. certificate/team.
  • Update notarization configuration to use the new ASC provider/team id and explicitly select notarytool.
  • Adjust notarization completion logging to reference the app path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
packages/bruno-electron/notarize.js Updates notarization parameters (tool/provider/team) and adjusts completion log output.
packages/bruno-electron/electron-builder-config.js Updates macOS signing identity to the Bruno Software, Inc. team certificate.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread packages/bruno-electron/notarize.js Outdated
@sid-bruno

Copy link
Copy Markdown
Collaborator Author
  1. We need to inform the users that the signing entity will be changing to Bruno Software, Inc.
  2. Requires builder to merge https://github.com/teambruno/bruno-builder/pull/66 in before merging this in.

cc: @bijin-bruno @lohit-bruno @helloanoop

@pull-request-size pull-request-size Bot added size/S and removed size/XS labels Jun 9, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/bruno-electron/notarize.js`:
- Around line 23-30: The notarize options object passed in
packages/bruno-electron/notarize.js currently includes ascProvider which is
invalid for tool: 'notarytool'; remove the ascProvider: 'P3WTZH48ZB' entry from
the options (keep tool: 'notarytool', appBundleId/appPath,
appleId/appleIdPassword, and teamId: 'P3WTZH48ZB') so authorization uses teamId
only and ensure APPLE_ID / APPLE_ID_PASSWORD are credentials for that same team;
update the options object referenced where notarize(...) or notarizeApp is
invoked to reflect this change.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: ed8df750-e302-400e-9466-f1c1cdff58b9

📥 Commits

Reviewing files that changed from the base of the PR and between ed5f5c2 and 01c85ba.

📒 Files selected for processing (2)
  • packages/bruno-electron/electron-builder-config.js
  • packages/bruno-electron/notarize.js

Comment on lines +23 to 30
tool: 'notarytool',
appBundleId: appId,
appPath: appPath,
appleId: process.env.APPLE_ID,
appleIdPassword: process.env.APPLE_ID_PASSWORD,
ascProvider: 'W7LPPWA48L'
ascProvider: 'P3WTZH48ZB',
teamId: 'P3WTZH48ZB'
});

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Does electron-notarize version 1.2.2 support the tool, teamId, and ascProvider options with notarytool?

💡 Result:

No. In electron-notarize version 1.2.2, the notarytool mode does not support the ascProvider option; it uses teamId instead. Evidence: In the electron/notarize package docs and code for the notarytool approach, authentication is configured with appleId/appleIdPassword (or an API key strategy) and requires teamId; the README example for notarytool uses teamId [1][2]. The source code for the notarytool submission builds authorization arguments with --team-id (derived from teamId) [3]. A reported issue notes notarytool mode fails if ascProvider is used/not provided as expected, and indicates ascProvider is required only for the legacy mode [4]. The commit that removed now-unusable legacy options also reflects that for the notarytool method you should use teamId rather than ascProvider [5]. So: - tool: yes (set tool: 'notarytool') — supported per types/docs [5][1] - teamId: yes (required for notarytool) [1][3][2] - ascProvider: no (not supported for notarytool; pertains to legacy) [4][5]

Citations:


Fix notarize options for tool: 'notarytool' (remove ascProvider)

electron-notarize v1.2.2’s notarytool flow uses teamId for authorization and does not support the legacy ascProvider option—so the ascProvider: 'P3WTZH48ZB' entry should be removed when tool: 'notarytool'. Keep tool: 'notarytool' and teamId: 'P3WTZH48ZB', and ensure APPLE_ID / APPLE_ID_PASSWORD belong to the same Apple team referenced by that teamId.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/bruno-electron/notarize.js` around lines 23 - 30, The notarize
options object passed in packages/bruno-electron/notarize.js currently includes
ascProvider which is invalid for tool: 'notarytool'; remove the ascProvider:
'P3WTZH48ZB' entry from the options (keep tool: 'notarytool',
appBundleId/appPath, appleId/appleIdPassword, and teamId: 'P3WTZH48ZB') so
authorization uses teamId only and ensure APPLE_ID / APPLE_ID_PASSWORD are
credentials for that same team; update the options object referenced where
notarize(...) or notarizeApp is invoked to reflect this change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants