-
Notifications
You must be signed in to change notification settings - Fork 133
fix: The specified item could not be found in the keychain #1448
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
37a1417
fix: The specified item could not be found in the keychain
kolipakakondal acf956f
fix: print diagnostics to check the issue
kolipakakondal 8a7414a
fix: add Apple Developer ID intermediate CAs
kolipakakondal 13eb446
fix: import AppleIncRootCertificate also
kolipakakondal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Critical:
pull_requesttrigger will overwrite production nightly artifacts and expose signing secrets on every PR.This workflow is not a build-only pipeline — downstream steps perform destructive, production-impacting actions that must not run for PRs:
aws s3 rm s3://${{ secrets.DL_BUCKET }}/dl/idf-eclipse-plugin/updates/nightly --recursivewipes the live nightly update site.Net effect: every PR merged-or-not against
master/release/**will replace the published nightly build with artifacts from an unmerged branch, and potentially sign/notarize unreviewed code with production credentials.If the intent is only to validate that the build/codesign/keychain change works in CI before merge, please either (a) revert this trigger and test via
workflow_dispatchon a branch, or (b) split the workflow so only the build + codesign verification steps run onpull_request, whileaz login, notarization, and all S3/CloudFront publishing steps remain gated toschedule(orpushtomaster).🛡️ Suggested minimal guard (Option B sketch)
At minimum, gate the publish/notarize steps so they never run for PRs. For example, add
if: github.event_name != 'pull_request'to each of:Authenticate to AzureGet Azure Key Vault Access TokenSign JAR files with Azure Key VaultNotarization of Espressif-IDE dmg filesUpload build assets to dl.espressif.com…and consider whether
Codesign Espressif-IDEitself should also be skipped on PR events, given the macOS cert secret exposure.Alternatively, keep the PR trigger only on a dedicated validation workflow that performs
mvn clean installand the keychain/codesign smoke test without secrets that touch production.🤖 Prompt for AI Agents