You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
Adds package caching to all CI jobs to avoid re-downloading NuGet and npm packages on every run.
Changes
cache: true added to all actions/setup-dotnet@v5 steps — enables automatic NuGet package caching keyed on the project lock files
cache: 'npm' added to all actions/setup-node@v5 steps — enables npm cache using package-lock.json
Impact
Affects all CI jobs: verify-linting, restore-project, build-javascript (×2 platforms), build-typescript, build-integration, build-standalone, build-python (×6 matrix), build-rust (×3 matrix), build-dart, build-beam, and analyzers (×4 matrix).
NuGet packages (FCS, FSharp.Core, etc.) are large — caching them should meaningfully reduce per-job setup time after the first run on a given lockfile state.
No risk
These changes only affect the CI setup phase; they do not touch build scripts, source code, or test logic.
Warning
Protected Files — Push Permission Denied
This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.
The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.
Create the pull request manually
# Download the patch from the workflow run
gh run download 23980596722 -n agent -D /tmp/agent-23980596722
# Create a new branch
git checkout -b repo-assist/eng-ci-caching-2026-04-2eb20ff86d846c03 main
# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-23980596722/aw-repo-assist-eng-ci-caching-2026-04.patch
# Push the branch and create the pull request
git push origin repo-assist/eng-ci-caching-2026-04-2eb20ff86d846c03
gh pr create --title '[Repo Assist] [Eng] Add NuGet and npm caching to CI workflow' --base main --head repo-assist/eng-ci-caching-2026-04-2eb20ff86d846c03 --repo fable-compiler/Fable
Note
🔒 Integrity filter blocked 84 items
The following items were blocked because they don't meet the GitHub integrity level.
🤖 This PR was created by Repo Assist, an automated AI assistant.
Summary
Adds package caching to all CI jobs to avoid re-downloading NuGet and npm packages on every run.
Changes
cache: trueadded to allactions/setup-dotnet@v5steps — enables automatic NuGet package caching keyed on the project lock filescache: 'npm'added to allactions/setup-node@v5steps — enables npm cache usingpackage-lock.jsonImpact
Affects all CI jobs:
verify-linting,restore-project,build-javascript(×2 platforms),build-typescript,build-integration,build-standalone,build-python(×6 matrix),build-rust(×3 matrix),build-dart,build-beam, andanalyzers(×4 matrix).NuGet packages (FCS, FSharp.Core, etc.) are large — caching them should meaningfully reduce per-job setup time after the first run on a given lockfile state.
No risk
These changes only affect the CI setup phase; they do not touch build scripts, source code, or test logic.
Warning
Protected Files — Push Permission Denied
This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.
Protected files
The push was rejected because GitHub Actions does not have
workflowspermission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.Create the pull request manually
Note
🔒 Integrity filter blocked 84 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".EntryPoint#2366list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: