Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 6. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v6) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
…/actions/checkout-6 chore(deps): bump actions/checkout from 4 to 6
--- updated-dependencies: - dependency-name: "@commitlint/cli" dependency-version: 20.4.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm_and_yarn - dependency-name: "@commitlint/config-conventional" dependency-version: 20.4.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm_and_yarn - dependency-name: "@google/gemini-cli" dependency-version: 0.29.5 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm_and_yarn - dependency-name: "@openai/codex" dependency-version: 0.104.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm_and_yarn - dependency-name: eslint dependency-version: 10.0.1 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
…pm_and_yarn-6c8cdb361e chore(deps): bump the npm_and_yarn group with 5 updates
Build C# LSP server for linux-x64, osx-arm64, win-x64 as self-contained single-file binaries. Generate csharp-lsp-manifest.json with SHA256 checksums and upload all assets to GitHub Release. This fixes LSP Performance CI failures caused by missing csharp-lsp-manifest.json in release assets. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Update actions/checkout v4→v6, actions/setup-dotnet v4→v5, and actions/upload-artifact v4→v6 to match other jobs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Walkthrough複数のGitHub Actionsワークフローでcheckoutアクションをv4からv6に更新。release.ymlに新しいbuild-lsp jobとLSP manifest生成機能を追加。Cargo.tomlおよびpackage.jsonファイルのバージョンを0.1.0から0.1.1に更新。devDependenciesの複数パッケージを更新。 Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
# Conflicts: # .github/workflows/release.yml
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (3)
.github/workflows/test.yml (1)
15-15: checkout v6 への更新は重複確認でOKactions/checkout@v6 の互換性確認は specs-readme のコメントと同様です。
Also applies to: 37-37, 51-51, 107-107
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/test.yml at line 15, The workflow step updated to use actions/checkout@v6 is fine but appears duplicated elsewhere; verify and consolidate the checkout action updates so all occurrences use actions/checkout@v6 consistently (the line with "uses: actions/checkout@v6" and the other occurrences referenced in the review), confirm v6 is compatible with our repo/specs-readme expectations, and remove or merge any redundant duplicate checkout steps to avoid running the same action multiple times in the workflow..github/workflows/lint.yml (1)
16-16: checkout v6 への更新は重複確認でOKactions/checkout@v6 の有効性確認は specs-readme のコメントと同様です。
Also applies to: 32-32
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/lint.yml at line 16, The workflow update to "uses: actions/checkout@v6" is duplicated; verify and consolidate both occurrences (the current one and the other at line with "Also applies to: 32-32") by confirming v6 is intended per the specs-readme comment, ensure both "uses: actions/checkout@v6" entries are consistent or remove the redundant one, and add a short commit message referencing the specs-readme verification to document the confirmation..github/workflows/release.yml (1)
24-24: checkout v6 への更新は重複確認でOKactions/checkout@v6 の有効性確認は specs-readme のコメントと同様です。
Also applies to: 103-103
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.github/workflows/release.yml at line 24, Confirm that replacing actions/checkout with actions/checkout@v6 is intentional and not a duplicate change: locate the workflow entry using the token "uses: actions/checkout" and ensure every occurrence (including the second occurrence flagged in the comment) is consistently updated to "uses: actions/checkout@v6"; run or simulate the workflow (CI/dry-run) to verify compatibility and, if the specs-readme guidance applies, note the verification result in the PR comment so reviewers know the v6 update is valid.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.github/workflows/specs-readme.yml:
- Line 15: このワークフローで指定している "uses: actions/checkout@v6" は v6 の認証情報格納変更に伴い既存スクリプトが
.git/config のトークンに依存していると失敗する可能性があります。該当ワークフロー（uses:
actions/checkout@v6）と関連スクリプトを確認し、.git/config
を直接参照する箇所があれば認証方法を明示的に切り替えてください：actions/checkout に persist-credentials: true
を明示的に設定するか、必要なリポジトリ操作は ${{ secrets.GITHUB_TOKEN }} を利用するよう変更し、Docker コンテナ内で認証付き
git コマンドを使う場合は Actions Runner を v2.329.0 以上にするか代替の認証セットアップ（環境変数でトークン注入や git
credential helper の設定）へ移行してください。
---
Duplicate comments:
In @.github/workflows/lint.yml:
- Line 16: The workflow update to "uses: actions/checkout@v6" is duplicated;
verify and consolidate both occurrences (the current one and the other at line
with "Also applies to: 32-32") by confirming v6 is intended per the specs-readme
comment, ensure both "uses: actions/checkout@v6" entries are consistent or
remove the redundant one, and add a short commit message referencing the
specs-readme verification to document the confirmation.
In @.github/workflows/release.yml:
- Line 24: Confirm that replacing actions/checkout with actions/checkout@v6 is
intentional and not a duplicate change: locate the workflow entry using the
token "uses: actions/checkout" and ensure every occurrence (including the second
occurrence flagged in the comment) is consistently updated to "uses:
actions/checkout@v6"; run or simulate the workflow (CI/dry-run) to verify
compatibility and, if the specs-readme guidance applies, note the verification
result in the PR comment so reviewers know the v6 update is valid.
In @.github/workflows/test.yml:
- Line 15: The workflow step updated to use actions/checkout@v6 is fine but
appears duplicated elsewhere; verify and consolidate the checkout action updates
so all occurrences use actions/checkout@v6 consistently (the line with "uses:
actions/checkout@v6" and the other occurrences referenced in the review),
confirm v6 is compatible with our repo/specs-readme expectations, and remove or
merge any redundant duplicate checkout steps to avoid running the same action
multiple times in the workflow.
ℹ️ Review info
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (2)
Cargo.lockis excluded by!**/*.lockpnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (8)
.github/workflows/lint.yml.github/workflows/release.yml.github/workflows/specs-readme.yml.github/workflows/test.ymlCHANGELOG.mdCargo.tomlUnityCliBridge/Packages/unity-cli-bridge/package.jsonpackage.json
| steps: | ||
| - name: Checkout code | ||
| uses: actions/checkout@v4 | ||
| uses: actions/checkout@v6 |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
actions/checkout v6 release notes breaking changes GitHub
💡 Result:
actions/checkout v6 release notes (and breaking/behavior changes)
- v6.0.0 (Nov 20, 2025) – Release notes: Node.js 24 support details/requirements; credentials are now persisted to a separate file (instead of being written into
.git/config); plus v6 docs/changelog updates. Potential breaking impact: anything that expected the auth token to be present in.git/configmay need updating. [1] - “What’s new” in the README for v6 clarifies the main behavior change:
persist-credentialsstores credentials in a separate file under$RUNNER_TEMP(git commands still work), and running authenticated git commands from a Docker container action requires Actions Runnerv2.329.0+. [2] - v6.0.1 (Dec 2, 2025) – Maintenance/docs/worktree-related updates; no explicit breaking changes called out. [1]
- v6.0.2 (Jan 9, 2026) – Adds
orchestration_idto the git user-agent when set; fixes tag-handling behavior; no breaking changes called out. [1]
Sources:
[1] actions/checkout releases page (v6.0.0–v6.0.2) (github.com)
[2] actions/checkout README (“Checkout v6 / What’s new”) (github.com)
Citations:
- 1: https://github.com/actions/checkout/releases
- 2: https://github.com/actions/checkout?utm_source=openai
actions/checkout@v6 への更新に伴う破壊的変更に対応が必要です
v6.0.0以降、認証情報の永続化方法が変更されました。従来の.git/configファイルへの記述から、$RUNNER_TEMP配下の別ファイルへの保存に切り替わったため、.git/config内の認証トークンに依存しているワークフローやスクリプトは動作しなくなる可能性があります。また、Docker コンテナアクション内で認証付き git コマンドを実行する場合は、Actions Runner v2.329.0以上が必須です。このワークフローが上記の依存関係を持つかどうか確認し、必要に応じて調整してください。
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.github/workflows/specs-readme.yml at line 15, このワークフローで指定している "uses:
actions/checkout@v6" は v6 の認証情報格納変更に伴い既存スクリプトが .git/config
のトークンに依存していると失敗する可能性があります。該当ワークフロー（uses:
actions/checkout@v6）と関連スクリプトを確認し、.git/config
を直接参照する箇所があれば認証方法を明示的に切り替えてください：actions/checkout に persist-credentials: true
を明示的に設定するか、必要なリポジトリ操作は ${{ secrets.GITHUB_TOKEN }} を利用するよう変更し、Docker コンテナ内で認証付き
git コマンドを使う場合は Actions Runner を v2.329.0 以上にするか代替の認証セットアップ（環境変数でトークン注入や git
credential helper の設定）へ移行してください。
Merged
This was referenced Mar 10, 2026
Merged
Merged
Merged
Merged
Merged
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.
Summary
Patch release that adds C# LSP server build and manifest generation to the release pipeline, enabling
lsp installto work from published releases.Changes
csharp-lsp-manifest.jsongeneration to release workflowVersion
v0.1.1
Closing Issues
None
Summary by CodeRabbit
リリースノート