| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR replaces the existing Python automation under .github/workflows/update-supported-enterprise-server-versions/ with a TypeScript implementation under pr-checks/, and updates the scheduled workflow to run the new script via Node/tsx.
Changes:
| File | Description |
|---|---|
| pr-checks/update-ghes-versions.ts | New TS implementation for determining supported GHES version range and updating src/api-compatibility.json. |
| pr-checks/update-ghes-versions.test.ts | Unit tests for the new TS script logic (parsing, date helpers, range selection). |
| pr-checks/package.json | Adds semver dependency for the new script. |
| pr-checks/config.ts | Exposes API_COMPATIBILITY_FILE path for use by the new script. |
| .github/workflows/update-supported-enterprise-server-versions.yml | Switches workflow execution from Python to Node/TypeScript and rebuilds after updating compatibility data. |
| .github/workflows/update-supported-enterprise-server-versions/update.py | Removes the previous Python implementation. |
| .github/workflows/update-supported-enterprise-server-versions/Pipfile | Removes Pipenv configuration no longer needed. |
| .github/workflows/update-supported-enterprise-server-versions/Pipfile.lock | Removes Pipenv lockfile no longer needed. |
| package-lock.json | Updates workspace dependency graph (including semver resolution). |
| lib/upload-lib.js | Generated artifact update due to dependency graph changes (not reviewed). |
| lib/entry-points.js | Generated artifact update due to dependency graph changes (not reviewed). |
Sorry, something went wrong.
|
@redsun82 Thanks for reviewing! There were some minor merge conflicts, which I have resolved now. Can you re-approve? :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Converts the Python code in .github/workflows/update-supported-enterprise-server-versions to TypeScript in pr-checks.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist