fsprojects / fsprojects/FSharp.Data
[repo-assist] Bump Fantomas to 7.0.6 and fix stale NuGet/login comment
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 874
- Forks
- 281
- Avg merge
- 55m
- Merged PRs (30d)
- 1
Description
🤖 This PR was created by Repo Assist, an automated AI assistant.
Changes
- Fantomas 7.0.1 → 7.0.6 (
.config/dotnet-tools.json): a safe patch-version bump of the code-formatting tool used byCheckFormat/Formatbuild targets. VerifiedCheckFormatreports "No files need formatting" with the new version, so no source reformatting was required. - Stale comment fix (
.github/workflows/push-master.yml): a previous Dependabot PR bumped the pinned SHA forNuGet/loginfrom v1.1.0 to v1.2.0, but left the adjacent# this hash is v1.1.0comment unchanged. Updated the comment to correctly say v1.2.0 to avoid confusing future maintainers/dependabot reviewers.
Rationale
Both are low-risk engineering hygiene fixes: keeping tooling current and keeping in-repo documentation/comments accurate and in sync with actual pinned versions.
Trade-offs
None identified — Fantomas 7.0.6 is a patch release within the same major/minor line already in use, and the comment fix is purely documentation.
Test Status
dotnet tool restore: ✅ succeeded, Fantomas 7.0.6 installeddotnet run --project build/build.fsproj -t CheckFormat: ✅ passed ("No files need formatting")dotnet run --project build/build.fsproj -t Build: ✅ succeeded, 0 errors (pre-existing warnings only, unrelated to this change)- Full
RunTestswas not executed for this docs/tooling-only change since it does not affect runtime or test code; Build + CheckFormat cover the affected surface.
[!WARNING]
Protected Files — Push Permission DeniedThis 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
# Download the patch from the workflow run
gh run download 33319289611 -n agent -D /tmp/agent-33319289611
# Create a new branch
git checkout -b repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717 main
# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-33319289611/aw-repo-assist-eng-fantomas-nuget-login-comment-2026-08-30.patch
# Push the branch and create the pull request
git push origin repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717
gh pr create --title '[repo-assist] Bump Fantomas to 7.0.6 and fix stale NuGet/login comment' --base main --head repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717 --repo fsprojects/FSharp.Data
Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again
Add this agentic workflow to your repo
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Update .config/dotnet-tools.json to use Fantomas 7.0.6 and correct the NuGet/login version comment in .github/workflows/push-master.yml. Start by reviewing the existing pinned versions, then run dotnet tool restore, CheckFormat, and Build. Done means the tool version and comment agree, formatting reports no changes, and the build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, github-actions
- Domain
- ci-cd, documentation, tooling
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100