filegrc 0.13.5 → 0.14.0

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 CHANGED
@@ -44,13 +44,13 @@ npx filegrc policy-library
44
44
 
45
45
  The command shows an exact diff only when the current text still matches the prior starter default. It skips customized, approved, active, superseded, and retired Policy content. Accept one named proposal revision only with the command printed by the review, which includes `--accept`, `--proposal-revision`, and `--yes`. Acceptance fails if the proposal changed after review. It changes only the listed defaults and does not approve a Policy, activate it, or mark a Control implemented.
46
46
 
47
- The normal runtime uses data model v6. Start a model v5 upgrade with a read-only preview:
47
+ The normal runtime uses data model v11. Existing model v10 workspaces start with a read-only preview:
48
48
 
49
49
  ```sh
50
- npx filegrc migrate --to-model 6 --preview --json
50
+ npx filegrc migrate --to-model 11 --preview --json
51
51
  ```
52
52
 
53
- Review every automatic, review-required, and unsupported item. Model v6 gives Training the same separate approval and activation lifecycle as other governed content. It preserves active model v5 Training with a visible legacy basis and removes Training schedule fields, because Obligations now own assignment timing. Resolve unsupported items before applying the same migration with `--yes`. The [model v6 upgrade guide](https://github.com/Alignbase/filegrc/blob/main/docs/upgrading-to-model-v6.md) documents the review.
53
+ Review every automatic, review-required, and unsupported item. Model v11 removes the old per-Control implementation approval fields. Owners can record implementation directly, while periodic Control oversight uses one Collection Review at the end of Step 3. Policy, Document, and Training approvals stay independent. Resolve unsupported items before applying the same migration with `--yes`. The [model v11 upgrade guide](https://github.com/Alignbase/filegrc/blob/main/docs/upgrading-to-model-v11.md) documents the review.
54
54
 
55
55
  A model v2 workspace must migrate to v3 first:
56
56
 
@@ -66,7 +66,7 @@ A model v1 workspace must migrate to v2 first:
66
66
  npx filegrc migrate --to-model 2 --preview --json
67
67
  ```
68
68
 
69
- Follow the [model v2 upgrade guide](https://github.com/Alignbase/filegrc/blob/main/docs/upgrading-to-model-v2.md), then run the model v3, v4, v5, and v6 previews in order.
69
+ Follow the [model v2 upgrade guide](https://github.com/Alignbase/filegrc/blob/main/docs/upgrading-to-model-v2.md), then migrate one model version at a time through model v11.
70
70
 
71
71
  `filegrc serve --help` prints bind, port, environment, and safety options without starting the server. The editable server prefers `127.0.0.1:8787` and chooses another available port when that port is occupied. Set `FILEGRC_HOST`, `FILEGRC_PORT`, or the matching flags when needed. In trunk mode, browser saves synchronize, commit, and push from the authoritative branch. Use `--allow-non-authoritative-writes` for local development in a task checkout; the override never commits or pushes.
72
72
 
package/model/index.js CHANGED
@@ -1,7 +1,7 @@
1
1
  import { readFileSync } from "node:fs";
2
2
 
3
- export const ACTIVE_MODEL_VERSION = "10";
4
- export const SUPPORTED_MODEL_VERSIONS = Object.freeze(["2", "3", "4", "5", "6", "7", "8", "9", ACTIVE_MODEL_VERSION]);
3
+ export const ACTIVE_MODEL_VERSION = "11";
4
+ export const SUPPORTED_MODEL_VERSIONS = Object.freeze(["2", "3", "4", "5", "6", "7", "8", "9", "10", ACTIVE_MODEL_VERSION]);
5
5
  export const MODEL_CAPABILITY_VERSIONS = Object.freeze({
6
6
  "guided-workflow": 3,
7
7
  "program-scope": 4,
@@ -16,7 +16,8 @@ export const MODEL_CAPABILITY_VERSIONS = Object.freeze({
16
16
  "rolled-up-obligations": 9,
17
17
  "temporal-collection-reviews": 9,
18
18
  "reporting-routes": 9,
19
- "reporting-route-sets": 10
19
+ "reporting-route-sets": 10,
20
+ "control-collection-oversight": 11
20
21
  });
21
22
 
22
23
  export function modelSupports(modelOrVersion, capability) {
@@ -31,9 +32,9 @@ export function modelSupports(modelOrVersion, capability) {
31
32
  export function loadModel(version = ACTIVE_MODEL_VERSION) {
32
33
  const requested = String(version);
33
34
  if (!SUPPORTED_MODEL_VERSIONS.includes(requested)) {
34
- const migrationTarget = requested === "1" ? "2" : requested === "2" ? "3" : requested === "3" ? "4" : requested === "4" ? "5" : requested === "5" ? "6" : requested === "6" ? "7" : requested === "7" ? "8" : requested === "8" ? "9" : "10";
35
+ const migrationTarget = requested === "1" ? "2" : requested === "2" ? "3" : requested === "3" ? "4" : requested === "4" ? "5" : requested === "5" ? "6" : requested === "6" ? "7" : requested === "7" ? "8" : requested === "8" ? "9" : requested === "9" ? "10" : "11";
35
36
  throw new Error(
36
- `Unsupported data model version "${requested}". This filegrc release supports models v2 through v10. `
37
+ `Unsupported data model version "${requested}". This filegrc release supports models v2 through v11. `
37
38
  + `Run \`npx filegrc migrate --to-model ${migrationTarget} --preview --json\` from the workspace root.`
38
39
  );
39
40
  }