chore(deps): update AWF_VERSION to 0.28.0 - #1896
Draft
github-actions[bot] wants to merge 1 commit into
Draft
Conversation
Updates the pinned AWF_VERSION constant from 0.27.32 to 0.28.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
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.
Dependency Update
Updates the pinned
AWF_VERSIONconstant insrc/compile/common.rsfrom0.27.32to0.28.0.Release
See the gh-aw-firewall release notes for details.
Action Items
If the upstream release notes describe changes that need follow-up in ado-aw, the workflow has recorded them on the canonical rolling issue
[deps-release-notes] awf — upstream release action items(as a new comment for this version range). If that issue does not yet exist, it was created; if the release was routine (patch-level fixes, internal refactors, no consumer-visible effect), no action items were recorded.This PR was opened automatically by the dependency version updater workflow.