Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 22 additions & 7 deletions .github/aw/actions-lock.json
Original file line number Diff line number Diff line change
@@ -1,19 +1,34 @@
{
"entries": {
"actions/checkout@v6.0.2": {
"repo": "actions/checkout",
"version": "v6.0.2",
"sha": "de0fac2e4500dabe0009e67214ff5f5447ce83dd"
},
"actions/download-artifact@v8.0.0": {
"repo": "actions/download-artifact",
"version": "v8.0.0",
"sha": "70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3"
},
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actions/download-artifact is locked here at v8.0.0 (sha 70fc10c…), but the generated workflow lockfiles reference actions/download-artifact v8.0.1 (sha 3e5f45b…). This mismatch can cause the workflow lock verification/compilation process to fail or drift. Update the entry to match the version/sha actually used (and/or add an entry for v8.0.1).

Suggested change
},
},
"actions/download-artifact@v8.0.1": {
"repo": "actions/download-artifact",
"version": "v8.0.1",
"sha": "3e5f45b"
},

Copilot uses AI. Check for mistakes.
"actions/github-script@v8": {
"repo": "actions/github-script",
"version": "v8",
"sha": "ed597411d8f924073f98dfc5c65a23a2325f34cd"
},
"github/gh-aw-actions/setup@v0.64.2": {
"repo": "github/gh-aw-actions/setup",
"version": "v0.64.2",
"sha": "f22886a9607f5c27e79742a8bfc5faa34737138b"
"actions/upload-artifact@v7.0.0": {
"repo": "actions/upload-artifact",
"version": "v7.0.0",
"sha": "bbbca2ddaa5d8feaa63e36b76fdaad77386f024f"
},
"github/gh-aw-actions/setup@v0.65.5": {
"github/gh-aw-actions/setup@v0.67.4": {
"repo": "github/gh-aw-actions/setup",
"version": "v0.65.5",
"sha": "15b2fa31e9a1b771c9773c162273924d8f5ea516"
"version": "v0.67.4",
"sha": "9d6ae06250fc0ec536a0e5f35de313b35bad7246"
},
"github/gh-aw/actions/setup@v0.52.1": {
"repo": "github/gh-aw/actions/setup",
"version": "v0.52.1",
"sha": "a86e657586e4ac5f549a790628971ec02f6a4a8f"
}
}
}
429 changes: 254 additions & 175 deletions .github/workflows/handle-bug.lock.yml

Large diffs are not rendered by default.

429 changes: 254 additions & 175 deletions .github/workflows/handle-documentation.lock.yml

Large diffs are not rendered by default.

429 changes: 254 additions & 175 deletions .github/workflows/handle-enhancement.lock.yml

Large diffs are not rendered by default.

429 changes: 254 additions & 175 deletions .github/workflows/handle-question.lock.yml

Large diffs are not rendered by default.

548 changes: 316 additions & 232 deletions .github/workflows/issue-classification.lock.yml

Large diffs are not rendered by default.

566 changes: 322 additions & 244 deletions .github/workflows/issue-triage.lock.yml

Large diffs are not rendered by default.

484 changes: 274 additions & 210 deletions .github/workflows/release-changelog.lock.yml

Large diffs are not rendered by default.

14 changes: 10 additions & 4 deletions .github/workflows/release-changelog.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,18 @@ Use the GitHub API to fetch the release corresponding to `${{ github.event.input

### Step 1: Identify the version range

1. The **new version** is the release tag: `${{ github.event.inputs.tag }}`
2. Fetch the release metadata to determine if this is a **stable** or **prerelease** release.
3. Determine the **previous version** to diff against:
1. **Before any `git log`, `git show`, tag lookup, or commit-range query, first convert the workflow checkout into a full clone by running:**
```bash
git fetch --prune --tags --unshallow origin || git fetch --prune --tags origin
```
This is **mandatory**. The workflow checkout may be shallow, which can make tag ranges and commit counts incomplete or outright wrong. Do not trust local git history until this command succeeds.
Comment on lines +51 to +53
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fallback git fetch --prune --tags origin will also run if --unshallow fails for reasons other than “repo already complete”, which can mask a real failure and leave the repo shallow (so commit ranges may still be incomplete). Prefer explicitly checking whether the repo is shallow (e.g., presence of .git/shallow) and only using the non---unshallow fetch when it isn’t, or ensure the command fails if the repo remains shallow after fetching.

Suggested change
git fetch --prune --tags --unshallow origin || git fetch --prune --tags origin
```
This is **mandatory**. The workflow checkout may be shallow, which can make tag ranges and commit counts incomplete or outright wrong. Do not trust local git history until this command succeeds.
if [ -f .git/shallow ]; then
git fetch --prune --tags --unshallow origin
else
git fetch --prune --tags origin
fi
if [ -f .git/shallow ]; then
echo "Repository is still shallow after fetch; refusing to continue." >&2
exit 1
fi

This is mandatory. The workflow checkout may be shallow, which can make tag ranges and commit counts incomplete or outright wrong. Do not trust local git history until this command succeeds and the repository is no longer shallow.

Copilot uses AI. Check for mistakes.
2. The **new version** is the release tag: `${{ github.event.inputs.tag }}`
3. Fetch the release metadata to determine if this is a **stable** or **prerelease** release.
4. Determine the **previous version** to diff against:
- **For stable releases**: find the previous **stable** release (skip prereleases). Check `CHANGELOG.md` for the most recent version heading (`## [vX.Y.Z](...)`), or fall back to listing releases via the API. This means stable changelogs include ALL changes since the last stable release, even if some were already mentioned in prerelease notes.
- **For prerelease releases**: find the most recent release of **any kind** (stable or prerelease) that precedes this one. This way prerelease notes only cover what's new since the last release.
4. If no previous release exists at all, use the first commit in the repo as the starting point.
5. If no previous release exists at all, use the first commit in the repo as the starting point.
6. After identifying the range, verify it by listing the commits in `PREVIOUS_TAG..NEW_TAG`. If the local result still looks suspiciously small or inconsistent, do **not** proceed based on local git alone — use the GitHub tools as the source of truth for the commits and PRs in the release.

### Step 2: Gather changes

Expand Down
456 changes: 267 additions & 189 deletions .github/workflows/sdk-consistency-review.lock.yml

Large diffs are not rendered by default.

Loading