Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 4 commits
- 38 files changed
- 2 contributors
Commits on Sep 9, 2026
-
Remove stale annotations and a dangling comment fragment (#426)
Drop leftover module-level annotation comments that carry no information, reword one inline annotation as a plain doc sentence, and remove a comment fragment in s3_client.rs orphaned by an earlier cleanup.
-
Reuse the on-host archive when the spec names a prior deployment
When a deployment spec references a prior deployment on the same host, DownloadBundle copies that deployment's unpacked archive and hard-links its bundle instead of downloading and extracting the revision again, which makes repeated deployments of the same revision substantially cheaper. Enabled by default; set enable_archive_reuse: false to always download. - Reuse falls back to a normal download whenever the referenced archive is missing, incomplete, or malformed, and never leaves a partial archive behind. - The referenced deployment id is validated before touching disk, and the AppSpec path is rejected if it climbs out of the archive. - Bundle-content hardening checks still run on every archive, reused or downloaded, as defense in depth. - The bundle ETag is carried forward on reuse so hooks keep seeing BUNDLE_ETAG even when the spec omits it. - Deployment diagnostics report whether the bundle was downloaded or reused, for observability. Bump the agent version to 2.1.0.
-
Re-stage only author-staged files in the pre-commit hook
The hook re-stages what its own auto-fix (fmt, clippy --fix) touched, but used git diff --name-only, which lists every modified file in the tree - silently sweeping deliberately-unstaged edits into the commit. Remember the staged set before the fixers run and re-stage only those files.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.0.1...v2.1.0