aidevops 3.32.334 → 3.32.336
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/VERSION +1 -1
- package/aidevops.sh +1 -1
- package/package.json +1 -1
- package/setup.sh +1 -1
package/README.md
CHANGED
|
@@ -72,7 +72,7 @@ The canonical purpose and architectural decision criteria are in
|
|
|
72
72
|
[](https://github.com/marcusquinn)
|
|
73
73
|
|
|
74
74
|
<!-- Release & Version Info -->
|
|
75
|
-
[](https://github.com/marcusquinn/aidevops/releases)
|
|
76
76
|
[](https://www.npmjs.com/package/aidevops)
|
|
77
77
|
[](https://github.com/marcusquinn/homebrew-tap)
|
|
78
78
|
[](https://github.com/marcusquinn/aidevops)
|
|
@@ -249,6 +249,8 @@ Running `aidevops security` with no arguments is the single command that covers
|
|
|
249
249
|
|
|
250
250
|
When a read guard identifies only a low-confidence source-code basename match, it emits a scoped request. A maintainer can run the displayed root-broker approval command. Approvals are bound to the exact runtime session, user, Git-tracked regular source path, approved content digest, and guard reason; they expire within 12 hours and never override private-key, environment-file, credential-store, hard-link, symlink, changed-content, cross-worktree, or untracked-file denials. Repeating `--path` while creating a request produces one exact, repository-bound manifest that a human can approve once. The plugin redirects each approved read to its root-controlled immutable snapshot; revocation removes the receipt and every snapshot.
|
|
251
251
|
|
|
252
|
+
To prepare source access before issue acceptance, use the [bundled approval workflow](.agents/reference/source-access-bundles.md). A durable metadata-only proposal identifies the intended linked worktree and source/test set; `aidevops approve issue <number> <owner/repo> --source-proposal <id>` presents one explicit human decision with independent issue and source signatures. The source grant lifetime starts at confirmation, not proposal creation. This command must run from a human terminal and requires a compatible released root broker.
|
|
253
|
+
|
|
252
254
|
Routine `aidevops update` never requests sudo or launches an editor. When the root-owned broker differs from the active release, update prints a machine-readable deferred action; a human runs `aidevops setup --scope source-access` in an attached terminal. Scoped setup verifies the published signed tag, invalidates inherited sudo, asks for one confirmation, has root fetch the exact reviewed broker bytes directly over TLS, compares those downloads byte-for-byte with the signed Git objects, creates a dedicated root-only signing key under `/etc/aidevops/source-access`, and invalidates sudo again. It never executes or copies the user-writable aidevops deployment as root. The plugin rejects approvals whenever installed broker bytes differ from the active release.
|
|
253
255
|
|
|
254
256
|
**Security advisories** are delivered via `aidevops update` and shown in the session greeting until dismissed. The scanner never exposes secret values — only file locations and key names. All remediation commands should be run in a separate terminal, not inside AI chat sessions.
|
package/VERSION
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
3.32.
|
|
1
|
+
3.32.336
|
package/aidevops.sh
CHANGED
package/package.json
CHANGED
package/setup.sh
CHANGED
|
@@ -17,7 +17,7 @@ fi
|
|
|
17
17
|
# AI Assistant Server Access Framework Setup Script
|
|
18
18
|
# Helps developers set up the framework for their infrastructure
|
|
19
19
|
#
|
|
20
|
-
# Version: 3.32.
|
|
20
|
+
# Version: 3.32.336
|
|
21
21
|
#
|
|
22
22
|
# Quick Install:
|
|
23
23
|
# npm install -g aidevops && aidevops update (recommended)
|