| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR optimizes resource usage by migrating lightweight automation workflows from ubuntu-latest to ubuntu-slim runners, which provide 1 vCPU and 5 GB RAM instead of the standard configuration. The change targets workflows that perform simple tasks like labeling PRs, updating version files, and publishing releases where the reduced resources are sufficient.
Key changes:
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
Show a summary per file| File | Description |
|---|---|
| .github/workflows/update-supported-enterprise-server-versions.yml | Updated runner type for the Enterprise Server versions update workflow |
| .github/workflows/update-release-branch.yml | Changed runner type for both update and backport jobs |
| .github/workflows/update-bundle.yml | Modified runner type for bundle update workflow |
| .github/workflows/publish-immutable-action.yml | Updated runner type for the action publishing workflow |
| .github/workflows/prepare-release.yml | Changed runner type for release preparation workflow |
| .github/workflows/post-release-mergeback.yml | Modified runner type for post-release merge-back workflow |
| .github/workflows/label-pr-size.yml | Updated runner type for PR size labeling workflow |
| .github/workflows/check-expected-release-files.yml | Changed runner type for release files validation workflow |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Save resources by using ubuntu-slim for lightweight workflows. This runner size has 1 vCPU and 5 GB RAM.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Dev/test only
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?
Merge / deployment checklist