Repository navigation
chore: use @veriworkly/ats-engine from npm; release 3.25.0 - #210
Merged
Merged
Conversation
The engine now lives in its own repository (VeriWorkly/ats-engine) and is published to npm as 0.1.0. The server, site and studio depend on ^0.1.0 instead of the workspace copy, which is removed along with its build steps in the root scripts, the app predev/prebuild hooks, both Dockerfiles and the CI workflows. The extraction-pool test builds its PDFs with the fixture it used before the engine moved into the monorepo, now back in apps/server/tests/ats/fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
What
@veriworkly/ats-enginefrom npm. The engine now lives in VeriWorkly/ats-engine and is published as 0.1.0 with provenance. This removes the workspace copy so only one engine exists.release-notes-v3.25.0.md.Changes
apps/server,apps/site,apps/studio: depend on@veriworkly/ats-engine@^0.1.0; engine build removed frompredev/prebuild.packages/ats-engine/(170 files). Its README, rubric, tests and history live in the engine repo.package.json:build:ats-engineand its uses removed.Dockerfile,apps/server/Dockerfile: no engine manifest/source copies or workspace install..github/workflows/tests.yaml: "Test ATS Engine" job removed (it runs in the engine repo); engine build steps removed. Same inbuilds.yaml.apps/server/tests/ats/fixtures/buildPdf.ts: the extraction-pool test's PDF fixture, back in the server's own tests.package-lock.json: engine resolved from the registry; sharedzod4.4.3 → 4.6.5 (the engine needs ≥4.6.5); the engine's dev tooling removed. No other version changes.Verification
tsc --noEmit: server, site, studio clean; server production build passes.apps/server/DockerfileandDockerfile(site) both build. Inside the server image the engine loads (0.1.0), scores a resume, and its/nodeentry and pdfjs resolve.Merging
Please use Create a merge commit (not squash or rebase). Then
Release-v3.25.0gets tagged onmasterwith the notes fromapps/server/scripts/seed-data/release-notes-v3.25.0.md.🤖 Generated with Claude Code