Skip to content

Add CI migration smoke test#1753

Merged
bokelley merged 1 commit intomainfrom
bokelley/kolkata-v12
Apr 5, 2026
Merged

Add CI migration smoke test#1753
bokelley merged 1 commit intomainfrom
bokelley/kolkata-v12

Conversation

@bokelley
Copy link
Copy Markdown
Contributor

Summary

  • add a dedicated GitHub Actions workflow to run built database migrations against PostgreSQL
  • stage server/src/db/migrations into dist/db/migrations so the CI path matches the Fly release artifact
  • trigger the smoke test on migration, DB runner, build, and workflow changes

Validation

  • staged dist/db/migrations locally to mirror the deploy artifact
  • ran DATABASE_URL=postgresql://postgres:postgres@127.0.0.1:55434/adcp_test2 node dist/db/migrate.js against a disposable Postgres instance
  • verified the run completed successfully through 340_purpose_mission_vision.sql

@gitguardian
Copy link
Copy Markdown

gitguardian bot commented Mar 30, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
29376516 Triggered Generic Password b681d3a .github/workflows/migration-smoke-test.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@bokelley bokelley merged commit 69af4e6 into main Apr 5, 2026
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant