remove legacy upload

[Zetazzz]

Summary

Removes the legacy REST POST /upload endpoint from graphql/server.

This endpoint used a separate upload-specific auth path, multer parsing, and streamToStorage() helper. Upload flows should now use GraphQL-backed paths instead of deriving /upload from a GraphQL endpoint.

Changes

• Removed graphql/server/src/middleware/upload.ts
  • createUploadAuthenticateMiddleware
  • uploadRoute
  • multer-based file parsing
  • upload-specific RLS/auth fallback logic
• Removed /upload route registration from graphql/server/src/server.ts
• Removed upload middleware exports from graphql/server/src/index.ts
• Removed streamToStorage() from graphile-settings
• Removed now-unused server dependencies:
  • multer
  • @types/multer
  • @pgsql/quotes
  • @constructive-io/upload-names
• Deleted legacy upload middleware tests
• Updated upload architecture docs to reflect the REST endpoint removal
• Added dashboard follow-up notes for known /upload consumers in packages/sheets

Dashboard Follow-Up

Dashboard still has runtime code that derives /upload from /graphql, mainly in the sheets upload flow. This PR documents that impact in:

graphile/graphile-upload-plugin/DASHBOARD_UPLOAD_FOLLOWUP.md

That dashboard work should migrate to a GraphQL-backed upload path separately.

Notes

This PR intentionally does not change the GraphQL multipart upload implementation or presigned upload flows. It only removes the historical REST upload endpoint and related dead server code.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​pgpm/​metaschema-schema@​0.18.0
	@​pgpm/​metaschema-modules@​0.21.1
	@​pgpm/​database-jobs@​0.18.0
	@​pgpm/​inflection@​0.18.0
	@​pgpm/​types@​0.18.0
	@​pgpm/​verify@​0.18.0
	@​launchql/​styled-email@​0.1.0
	@​pgpm/​services@​0.18.0
	@​jest/​test-sequencer@​30.4.1
	@​launchql/​mjml@​0.1.1
	@​inquirerer/​utils@​3.3.7
	@​constructive-io/​fetch@​1.1.1
	@​agentic-kit/​ollama@​2.0.0
	@​inquirerer/​test@​1.4.1
	@​dataplan/​json@​1.0.0
	@​babel/​generator@​7.29.1
	@​constructive-io/​noble-hashes@​0.2.1
	@​0no-co/​graphql.web@​1.2.0
	@​aws-sdk/​lib-storage@​3.1052.0
	@​graphile-contrib/​pg-many-to-many@​2.0.0-rc.2
	@​pgsql/​traverse@​17.2.6
	@​pgsql/​utils@​17.8.17
	@​aws-sdk/​client-s3@​3.1052.0
	@​aws-sdk/​s3-request-presigner@​3.1052.0
	@​playwright/​test@​1.60.0

View full report

[socket-security]

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		Obfuscated code: npm @launchql/protobufjs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@launchql/protobufjs@7.2.6 ℹ 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/@launchql/protobufjs@7.2.6. 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		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@noble/hashes@1.8.0 ℹ 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/@noble/hashes@1.8.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		Obfuscated code: npm @noble/hashes is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/@noble/hashes@1.8.0 ℹ 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/@noble/hashes@1.8.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