Records that a consumer pinned to the previous version keeps working (MIL-004 criterion 3).
Evidence: RepoFoundry callers at @v1.0.0 and @v1 after v1.0.1 (run 660); at @v1.1.0 with tools-ref: v1.1.0 and at @v1 after v1.1.0 (run 672). v1.0.0 still points to 97ffa49.
MIL-004 Verification results criterion 3 and RC-048 (verdict and action item) say so; both get a new Version History row.
No wiki pages changed: only milestone and review documents changed.
No issue closed: records the verification requested by the user.
Records that a consumer pinned to the previous version keeps working (MIL-004 criterion 3).
- Evidence: RepoFoundry callers at `@v1.0.0` and `@v1` after `v1.0.1` (run 660); at `@v1.1.0` with `tools-ref: v1.1.0` and at `@v1` after `v1.1.0` (run 672). `v1.0.0` still points to `97ffa49`.
- MIL-004 Verification results criterion 3 and RC-048 (verdict and action item) say so; both get a new Version History row.
No wiki pages changed: only milestone and review documents changed.
No issue closed: records the verification requested by the user.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Records that a consumer pinned to the previous version keeps working (MIL-004 criterion 3).
@v1.0.0and@v1afterv1.0.1(run 660); at@v1.1.0withtools-ref: v1.1.0and at@v1afterv1.1.0(run 672).v1.0.0still points to97ffa49.No wiki pages changed: only milestone and review documents changed.
No issue closed: records the verification requested by the user.