Prod: add vacancy city metadata API - #711
Merged
Merged
Conversation
TThanos3000
marked this pull request as ready for review
August 27, 2026 09:48
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Production port of the vacancy city metadata functionality verified on dev in PR #706 (feature commit
446cab5820ff32e0b74d7ec82a5f4fbf28df5d2d). The port is applied semantically on top of currentmasterbase1aee63c8a506404282170909152da3756bd80255;devwas not merged and its merge/deploy fixes were not cherry-picked.Changes
Vacancy.city(max_length=255) through migrationvacancy.0010_vacancy_city;смешаннаяand stores/returns canonicalсмешанный формат;cityin create, detail, list, catalog, legacy project nested, and workspace vacancy contracts;Production-only behavior preserved
VacancyCatalogSerializerand public catalog contract;master.No production file was replaced wholesale with its dev version.
Migration impact
vacancy/migrations/0010_vacancy_city.pyfollows0009_vacancy_specializationand only adds a nullable column. Existing production vacancies remain valid withcity = NULL; no data backfill fromProject.regionis performed.Checks
python manage.py check --tag models: passedpython manage.py makemigrations --check --dry-run --skip-checks: passed (No changes detected)vacancy 0009 -> 0010,0010is the leafpython -m compileall: passedgit diff --check: passedLocal PostgreSQL was unavailable, so targeted DB tests could not run separately on Windows; every targeted vacancy/workspace test is included in and passed by the full PostgreSQL CI suite. The ordinary local
manage.py checkis blocked by the missing Windows WeasyPrintgobject-2.0-0system library; Django system checks ran successfully as part of the Linux CI test command.Scope confirmation
Changed files are limited to vacancy model/constants/serializers/migration/tests and one project workspace vacancy contract test. React, Angular/frontend, workflows, Docker/deploy, infrastructure, and unrelated backend modules are unchanged.