Skip to content

fix (db): update db-migration to create swaps i823#1301

Open
JustKuzya wants to merge 8 commits into
devfrom
jk/db-swaps-upgrade-i823
Open

fix (db): update db-migration to create swaps i823#1301
JustKuzya wants to merge 8 commits into
devfrom
jk/db-swaps-upgrade-i823

Conversation

@JustKuzya

Copy link
Copy Markdown
Collaborator
  • add guide for testing the database upgrade with containerized Postgres DBMS
  • create migration script for swaps
  • verify that the script works for SQLite and containerized Postgres

- add guide for testing the database upgrade with containerized postgres DBMS
- create migration script for swaps
- verify that the script works for SQLite and containerized Posgres
@jtsextonMITRE jtsextonMITRE self-assigned this Jun 4, 2026

@keithmanville keithmanville left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I was expecting to see the JobSwaps ORM object in db/models/jobs.py and changes to the response schema in v1/jobs/schema.py. Did you forget to commit? It looks like you had this done if you generated the alembic script from the ORM.

henrychoy and others added 7 commits June 15, 2026 08:08
Lint and format the frontend using npm run lint and npm run format from the src/frontend directory.
Perform check only using npm run lint:check and npm run format:check.

Updated `DEVELOPER.md` to note lint and format rules.

Updated all frontend packages.

Note: eslint is incompatible with node v23. Added .nvmrc so nvm can be used to to switch to node
v22. Added short explanation in frontend README.
Added frontend-checks.yml which runs the lint:check and format:check for PRs.
- added method doc-strings
- changed the commit messafge structure to space-less one
- create ORM mapping in model
- regenerate upgrade script
- update the model with job_id+
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.

3 participants