You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: distribute ado-aw via GitHub Releases instead of ADO pipeline artifacts
Replace DownloadPipelineArtifact@2 tasks (pipeline 2437, project 4x4) in both
standalone and 1ES templates with curl downloads from GitHub Releases, verified
via SHA256 checksums. The compiler embeds its own CARGO_PKG_VERSION at compile
time so generated pipelines always fetch the matching release.
Changes:
- Add .github/workflows/release.yml (triggered on v* tags)
- Update templates/base.yml and templates/1es-base.yml (6 download sites)
- Add {{ compiler_version }} marker replacement in both compilers
- Add integration test assertions for new download mechanism
- Document {{ compiler_version }} marker in AGENTS.md
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat: automate releases with release-please
Replace manual tag-triggered release with release-please automation:
- On push to main, release-please maintains a Release PR with changelog
and Cargo.toml version bump (based on conventional commits)
- Merging the Release PR creates the git tag and GitHub Release
- Build job then compiles the binary and uploads assets to the release
Bump logic: fix: →
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: checksum verification filename mismatch and pin action versions
Fix critical bug where sha256sum --check would always fail because the
binary was downloaded as 'ado-aw' but the checksum file references
'ado-aw-linux-x64'. Now downloads as 'ado-aw-linux-x64', verifies the
checksum, then renames to 'ado-aw'. Fixed in all 6 download blocks
across both templates.
Also:
- Pin GitHub Actions to commit SHAs for supply-chain security
- Add set -euo pipefail to release asset preparation step
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: add --clobber to release upload and test compiled output markers
- Add --clobber to gh release upload for idempotent retries
- Add integration test that compiles a fixture through the binary and
verifies no unreplaced {{ markers }} remain in the output, confirming
{{ compiler_version }} is correctly substituted
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: AGENTS.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -573,6 +573,17 @@ Generates environment variable entries for the copilot AWF step when `read-only-
573
573
574
574
If no `read-only-service-connection` is configured, this marker is replaced with an empty string, and ADO access tokens are omitted from the copilot invocation.
575
575
576
+
## {{ compiler_version }}
577
+
578
+
Should be replaced with the version of the `ado-aw` compiler that generated the pipeline (derived from `CARGO_PKG_VERSION` at compile time). This version is used to construct the GitHub Releases download URL for the `ado-aw` binary.
579
+
580
+
The generated pipelines download the compiler binary from:
A SHA256 checksum file (`ado-aw-linux-x64.sha256`) is also downloaded and verified to ensure binary integrity. This replaces the previous approach of downloading from an internal ADO pipeline artifact.
586
+
576
587
### 1ES-Specific Template Markers
577
588
578
589
The following markers are specific to the 1ES target (`target: 1es`) and are not used in standalone pipelines:
@@ -944,7 +955,7 @@ mcp-servers:
944
955
945
956
Network isolation is provided by AWF (Agentic Workflow Firewall), which provides L7 (HTTP/HTTPS) egress control using Squid proxy and Docker containers. AWF restricts network access to a whitelist of approved domains.
946
957
947
-
The AWF binary is downloaded from an internal ADO pipeline (pipeline 2450, branch `ms/main`, artifact `gh-aw-firewall-linux-x64`). Docker is sourced via the `DockerInstaller@0` ADO task.
958
+
The `ado-aw` compiler binary is distributed via [GitHub Releases](https://github.com/githubnext/ado-aw/releases) with SHA256 checksum verification. The AWF binary is downloaded from an internal ADO pipeline (pipeline 2450, branch `ms/main`, artifact `gh-aw-firewall-linux-x64`). Docker is sourced via the `DockerInstaller@0` ADO task.
0 commit comments