Skip to content

Fix observable module-pin preconditions and failed-release identity - #200

Merged
rldyourmnd merged 1 commit into
mainfrom
fix/observable-module-pin-preconditions
Sep 29, 2026
Merged

rldyourmnd merged 1 commit into
mainfrom
fix/observable-module-pin-preconditions

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Changes

  • Preserve stable finding codes when module-pin preconditions go stale, so the journal names the cause without storing raw provider diagnostics.
  • Isolate declared module verification lanes from host Git configuration that can start background fsmonitor processes and produce false unjoined-descendant failures.
  • Advance release identity past an already-tagged failed bundle. With failed 0.9.17/sequence 72, the next successful candidate is 0.9.18/sequence 73.

Verification

  • go test ./core/app ./core/operations
  • python3 -m pytest -q (70 passed, 9 subtests)
  • scripts/validate_shell.sh
  • Release resolver exercised against mocked successful and failed latest envelopes.
  • go test ./... and scripts/validate_go_core.sh --quick are running locally; required CI will also prove them.

Record stable observation finding codes in stale-precondition journal events, isolate module verification from host Git configuration, advance release identity past failed tags, and restamp generated projections.
@rldyourmnd
rldyourmnd force-pushed the fix/observable-module-pin-preconditions branch from 3d64e2c to 31636ef Compare September 29, 2026 09:43
@rldyourmnd
rldyourmnd merged commit ee48ad5 into main Sep 29, 2026
8 checks passed
@rldyourmnd
rldyourmnd deleted the fix/observable-module-pin-preconditions branch September 29, 2026 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant