release: v7.0.0 - #538
Merged
Merged
Conversation
bosesuneha
force-pushed
the
release/v7.0.0
branch
from
June 23, 2026 18:46
28436ae to
848469a
Compare
Closed
Tatsinnit
reviewed
Jun 30, 2026
Tatsinnit
approved these changes
Jun 30, 2026
Addresses review feedback on PR Azure#538 by documenting the recommended practice of pinning the action to a full commit SHA for supply-chain security, in line with GitHub's hardening guidance.
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
3 participants
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.
Summary
Cuts v7.0.0 of
Azure/k8s-deploy. Merging this PR will triggerrelease-pr.yml, which tagsv7.0.0, moves thev7major tag, and publishes the GitHub Release.Breaking change
manifests:inputs that resolve outsideGITHUB_WORKSPACE(via../, absolute paths, or symlinks) now fail the action with a clear error. Workflows that depend on reading manifests from outside the workspace (uncommon; mostly self-hosted runners) must move those files into the workspace before invoking this action. This is why the major version is bumped.What's included since v6.0.0
14 commits — see
CHANGELOG.mddiff for the full list. Headlines:GITHUB_WORKSPACE, URL fetcher hardeningFile changes
CHANGELOG.md— new[7.0.0]entry at top, formatted to match prior entriespackage.json+package-lock.json—6.0.0→7.0.0README.md— bumped 11 usage examples fromAzure/k8s-deploy@v5→@v7(note:@v5was never updated to@v6in docs: update action version references in README to latest majors #500, so this catches up to two majors at once)Pre-merge checklist
npm cicleannpm run typecheckcleannpm run buildclean (esbuild bundle 1.1mb)npm test— 271/271 passing (one cleanup-timing test from fix: confine manifest paths to workspace and harden URL fetcher #528 was flaky on first run; consistently passes on retry, worth a follow-up)package.json+ lockfile@v5→@v7(11 occurrences)Post-merge verification
Release Projectworkflow run is greengh release view v7.0.0 --repo Azure/k8s-deployexists with the changelog bodygit ls-remote --tags https://github.com/Azure/k8s-deploy.git | grep -E 'v7(\.0\.0)?$'shows bothv7andv7.0.0at the merge SHA@v7and confirm it runsFollow-ups (not blocking)
removes temp file on mid-stream response errortest infileUtils.test.ts— likely needs a deterministic wait for the cleanup promise rather thanwaitForCleanup().