Copilot commented on code in PR #13351:
URL: https://github.com/apache/cloudstack/pull/13351#discussion_r3362763759


##########
.github/workflows/issue-triage-agent.lock.yml:
##########
@@ -92,7 +92,7 @@ jobs:
     steps:
       - name: Setup Scripts
         id: setup
-        uses: 
github/gh-aw-actions/setup@46d564922b082d0db93244972e8005ea6904ee5f # v0.76.1
+        uses: 
github/gh-aw-actions/setup@97f280b14527ca95859c0facba201aeccb2c097f # v0.77.3
         with:

Review Comment:
   This lock workflow now uses github/gh-aw-actions/setup@97f280b… (v0.77.3), 
but the embedded `# gh-aw-manifest:` header at the top of the file still lists 
github/gh-aw-actions/setup@46d5649… (v0.76.1). That makes the lock file 
internally inconsistent (and the “Custom actions used” section no longer 
matches the manifest), which can confuse reviewers and may break any tooling 
that relies on the manifest header.



##########
.github/workflows/daily-repo-status.lock.yml:
##########
@@ -91,7 +91,7 @@ jobs:
     steps:
       - name: Setup Scripts
         id: setup
-        uses: 
github/gh-aw-actions/setup@46d564922b082d0db93244972e8005ea6904ee5f # v0.76.1
+        uses: 
github/gh-aw-actions/setup@97f280b14527ca95859c0facba201aeccb2c097f # v0.77.3
         with:

Review Comment:
   This lock workflow now uses github/gh-aw-actions/setup@97f280b… (v0.77.3), 
but the `# gh-aw-manifest:` header at the top of the file still lists 
github/gh-aw-actions/setup@46d5649… (v0.76.1). That makes the lock file 
internally inconsistent and can cause downstream tooling or reviewers to rely 
on stale pinned SHAs.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to