Fix milestone-changelog title-prefix causing blank issue title#16430
Open
Fix milestone-changelog title-prefix causing blank issue title#16430
Conversation
Contributor
|
🚀 Dogfood this PR with:
curl -fsSL https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 16430Or
iex "& { $(irm https://raw.githubusercontent.com/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 16430" |
JamesNK
force-pushed
the
update-gh-aw-v0.71.0
branch
from
376018a to
f18a419
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository’s generated Agentic Workflows (gh-aw) lock files to reflect compiling with gh-aw v0.71.0, including updated action SHAs and container image pinning used by the locked workflows.
Changes:
- Bump gh-aw compiler/runtime references in workflow lock files to
v0.71.0and refresh the generated manifests. - Update pinned container images (AWF firewall + MCP gateway) and add
actions/setup-nodeusage in the generated workflows. - Update
.github/aw/actions-lock.jsonentries for gh-aw setup actions tov0.71.0(and addsetup-cli).
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/aw/actions-lock.json | Updates gh-aw action lock entries to v0.71.0 and adds setup-cli. |
| .github/workflows/daily-repo-status.lock.yml | Recompiled lock workflow with v0.71.0; updates pinned images/actions and runtime env defaults. |
| .github/workflows/milestone-changelog.lock.yml | Recompiled lock workflow with v0.71.0; updates pinned images/actions and runtime env defaults. |
| .github/workflows/pr-docs-check.lock.yml | Recompiled lock workflow with v0.71.0; updates pinned images/actions and runtime env defaults. |
| .github/workflows/repo-pulse.lock.yml | Recompiled lock workflow with v0.71.0; updates pinned images/actions and runtime env defaults. |
Comments suppressed due to low confidence (2)
.github/workflows/daily-repo-status.lock.yml:1138
- The fallback for
COPILOT_MODELchanged from empty to a specific model (claude-sonnet-4.6). That’s a behavior change and can make the detection run metadata inconsistent withGH_AW_INFO_MODEL(fallbackauto). Consider keeping the previous behavior (empty/auto) or aligning the fallback used for both the info block and the detection invocation.
GITHUB_SERVER_URL: ${{ github.server_url }}
.github/workflows/daily-repo-status.lock.yml:697
- The fallback for
COPILOT_MODELchanged from empty to a specific model (claude-sonnet-4.6). That’s a behavior change (and affects reproducibility/cost/availability) and also makes the run metadata inconsistent withGH_AW_INFO_MODEL(fallbackauto). Consider keeping the previous behavior (empty/auto) or aligning the fallback used for both the info block and the actual Copilot CLI invocation.
GH_AW_PROMPT: /tmp/gh-aw/aw-prompts/prompt.txt
| @@ -725,9 +748,10 @@ jobs: | |||
| GH_AW_PHASE: agent | |||
| GH_AW_PROMPT: /tmp/gh-aw/aw-prompts/prompt.txt | |||
There was a problem hiding this comment.
The fallback for COPILOT_MODEL changed from empty to a specific model (claude-sonnet-4.6). That’s a behavior change (and affects reproducibility/cost/availability) and also makes the run metadata inconsistent with GH_AW_INFO_MODEL (fallback auto). Consider keeping the previous behavior (empty/auto) or aligning the fallback used for both the info block and the actual Copilot CLI invocation.
| GITHUB_COPILOT_INTEGRATION_ID: agentic-workflows | ||
| GITHUB_HEAD_REF: ${{ github.head_ref }} | ||
| GITHUB_REF_NAME: ${{ github.ref_name }} | ||
| GITHUB_SERVER_URL: ${{ github.server_url }} |
There was a problem hiding this comment.
The fallback for COPILOT_MODEL changed from empty to a specific model (claude-sonnet-4.6). That’s a behavior change and can make the detection run metadata inconsistent with GH_AW_INFO_MODEL (fallback auto). Consider keeping the previous behavior (empty/auto) or aligning the fallback used for both the info block and the detection invocation.
JamesNK
changed the title
…luded in changelog
This was referenced Apr 24, 2026
…, Breaking changes)
Contributor
|
Re-running the failed jobs in the CI workflow for this pull request because 2 jobs were identified as retry-safe transient failures in the CI run attempt.
|
Contributor
|
🎬 CLI E2E Test Recordings — 73 recordings uploaded (commit View all recordings
📹 Recordings uploaded automatically from CI run #24929843764 |
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
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.
Description
Fix the Milestone Changelog Generator workflow failing to create issues due to a blank title being sent to the GitHub API.
The
title-prefixin thesafe-outputsconfiguration was set to the entire issue title ("[13.3] Change log"), so after the handler stripped the prefix from the agent-provided title, nothing remained — resulting in a blank title and a 422 validation error from the API.Changed
title-prefixfrom"[13.3] Change log"to"[13.3] "for bothcreate-issueandupdate-issuesafe outputs, consistent with how other workflows use the prefix (e.g.,"[13.2-burndown] ","[docs] ","[repo-pulse]"). Recompiled the lock file with gh-aw v0.69.0.Checklist
<remarks />and<code />elements on your triple slash comments?aspire.devissue: