Conversation
feat: add editable career FAQ section
ci: build and deploy container images
Feat/career improvements
Feat/security updates
fix: update recruitment navigation labels in both languages
Transfer career groups, settings and referenced images through explicit mappings and reviewed plans. Bind imports to the target database, verify content in a transaction, and preserve rollback receipts. Package the server runner in the application image and add transfer checks to CI and releases.
feat(career): Add validated staging content transfer
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Release the career-page changes validated on staging. The new
/karrierpage replaces recruitment navigation and supports bilingual groups and positions, editable FAQs and application fields, private PDF CV uploads, and Google Sheets export. Include the dependency security updates, schema repairs, and container deployment workflow already running on staging.Career content is promoted separately using the bundled Payload importer. The importer keeps production group IDs, takes career content and application settings from staging, validates a target-bound plan, and applies the transfer in a transaction. Merging or deploying this PR does not copy staging records into production.
Validation:
b3c9c2apassed release validation, image publication and VPS deployment in run 34163134968.Production sequence:
NEXT_PUBLIC_SERVER_URL=https://frtbme.huin the production application environment before deployment. GitHub's ProductionPUBLIC_URLnow uses this address. Current server storage has 7.6 GB free; the staging content has not changed since the reviewed export. Both environments use a database namedfrtin separate PostgreSQL containers. Verify backup availability before release.main. Production deployment creates a database/CV backup, runs migrations, mounts private CV storage and checks application health.docs/career-content-transfer.md.Backups, content exports, applicant data and credentials are not included in the release.