Fix release notes never being included in Slack notifications#796
Open
Fix release notes never being included in Slack notifications#796
Conversation
Co-authored-by: Vetle444 <35739538+Vetle444@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate missing release notes in Slack posts
Fix release notes never being included in Slack notifications
Feb 27, 2026
Vetle444
approved these changes
Feb 27, 2026
Vetle444
approved these changes
Feb 27, 2026
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug where release notes were always empty in Slack notifications posted by the publishApp build task. The issue was caused by two bugs in the changelog parsing pipeline: (1) using string literal matching instead of regex matching, and (2) using an incorrect header pattern that included a date suffix not present in the actual CHANGELOG.md format.
Changes:
- Fixed
VersionUtil.GetReleaseNotesFromChangelogto useRegex.IsMatchinstead ofstring.Containsfor pattern matching - Corrected the changelog header pattern in
build.csxto match the actual format## [X.Y.Z]with properly escaped brackets - Updated CHANGELOG.md with patch version 55.2.3
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| build/build.csx | Fixed changelog header pattern from ## [[0-9]+.[0-9]+.[0-9]+] - [0-9]+-[0-9]+-[0-9]+ to ## \\[{VersionPattern}\\] to match actual CHANGELOG format |
| build/AwesomeBuildsystem/Core/VersionUtil.csx | Changed line.Contains(changelogHeader) to Regex.IsMatch(line, changelogHeader) to properly match regex patterns |
| CHANGELOG.md | Added entry for version 55.2.3 documenting this build fix |
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 of Change
Release notes are always empty in Slack messages posted by
publishApp. Two bugs in the changelog parsing pipeline:VersionUtil.GetReleaseNotesFromChangelogusesline.Contains(changelogHeader)— literal string match against a regex pattern string. Never matches.build.csxpasses header pattern## [[0-9]+.[0-9]+.[0-9]+] - [0-9]+-[0-9]+-[0-9]+which includes a date suffix (- YYYY-MM-DD) that doesn't exist in the CHANGELOG (format is just## [55.2.2]).Fixes:
VersionUtil.csx:line.Contains(changelogHeader)→Regex.IsMatch(line, changelogHeader)build.csx: Pattern changed to## \[[0-9]+.[0-9]+.[0-9]+\]— matches actual CHANGELOG format, properly escapes bracketsTodos
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.