Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat(functions): add storage-confirm-upload function#69

Open
theothersideofgod wants to merge 5 commits into
main from
feat/storage-confirm-upload
Open

feat(functions): add storage-confirm-upload function #69
theothersideofgod wants to merge 5 commits into
main from
feat/storage-confirm-upload

Conversation

@theothersideofgod

@theothersideofgod theothersideofgod commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add storage-confirm-upload function for deferred upload confirmation via HeadObject check
  • Add minio service to docker-compose for local S3 testing
  • Fix db-setup image (was pointing to wrong image)
  • Update API configuration for tenant support

Changes

  • functions/storage-confirm-upload/ - new function
  • docker-compose.yml - add minio, fix images, update config
  • skaffold.yaml - add profile for storage-confirm-upload

Test plan

  • Provision database with storage_module has_confirm_upload=true
  • Upload file as tenant user
  • Verify file status changes to 'uploaded'

🤖 Generated with Claude Code

theothersideofgods and others added 4 commits June 10, 2026 16:51
Handles deferred upload confirmation via HeadObject check.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add minio service for local S3 testing
- Fix db-setup image (was pointing to wrong image)
- Add S3/MinIO environment variables
- Update API configuration for tenant support
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

socket-security Bot commented Jun 10, 2026
edited
Loading

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added npm/​@​pgpmjs/​logger@​1.5.0 73 100 100 95 100
Added npm/​@​pgpmjs/​logger@​2.12.0 73 100 100 96 100
Added npm/​pg-cache@​3.12.0 74 100 100 98 100
Added npm/​graphile-llm@​0.11.0 76 100 100 96 100
Added npm/​@​aws-sdk/​client-s3@​3.1060.0 99 100 100 98 100

View full report

socket-security Bot commented Jun 10, 2026
edited
Loading

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @internationalized/date is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/graphile-llm@0.11.0npm/@internationalized/date@3.12.2

i Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@internationalized/date@3.12.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm markdown-it is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: pnpm-lock.yamlnpm/graphile-llm@0.11.0npm/markdown-it@14.2.0

i Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/markdown-it@14.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm react-stately is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/graphile-llm@0.11.0npm/react-stately@3.47.0

i Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/react-stately@3.47.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Anmol1696 Anmol1696 Awaiting requested review from Anmol1696

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /