Skip to content

release: promote verified Issue #783 integration - #809

Draft
Serph91P wants to merge 20 commits into
mainfrom
develop
Draft

release: promote verified Issue #783 integration#809
Serph91P wants to merge 20 commits into
mainfrom
develop

Conversation

@Serph91P

@Serph91P Serph91P commented Aug 22, 2026

Copy link
Copy Markdown
Owner

Promotion of verified Issue #783 integration from develop to main.

Immutable candidate head: 969d87826b39cb004da2de723462a6d64c2dd326.
Immutable main base: 5cba015cf5b741040c8f2b4ea45a67dc755fad42.

Source PR #808 and bounded P1 remediation PR #810 were merged to develop. Fresh current-head CodeQL, Tests, Security Scanning, Docker Build Test, and Release & Docker Build checks completed successfully for the immutable candidate.

This Draft requires fresh detached exact-head technical gate t_e9801575, security gate t_117ddc3c, and explicit Max authorization before merge to main.

dependabot Bot and others added 18 commits August 20, 2026 07:47
Bumps the python-dependencies group with 1 update: [python-dotenv](https://github.com/theskumar/python-dotenv).


Updates `python-dotenv` from 1.2.2 to 1.2.3
- [Release notes](https://github.com/theskumar/python-dotenv/releases)
- [Changelog](https://github.com/theskumar/python-dotenv/blob/main/CHANGELOG.md)
- [Commits](theskumar/python-dotenv@v1.2.2...v1.2.3)

---
updated-dependencies:
- dependency-name: python-dotenv
  dependency-version: 1.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps the npm-dependencies group in /app/frontend with 2 updates: [@tsconfig/node24](https://github.com/tsconfig/bases/tree/HEAD/bases) and [vue-tsc](https://github.com/vuejs/language-tools/tree/HEAD/packages/tsc).


Updates `@tsconfig/node24` from 24.0.4 to 24.0.5
- [Commits](https://github.com/tsconfig/bases/commits/HEAD/bases)

Updates `vue-tsc` from 3.3.9 to 3.3.10
- [Release notes](https://github.com/vuejs/language-tools/releases)
- [Changelog](https://github.com/vuejs/language-tools/blob/master/CHANGELOG.md)
- [Commits](https://github.com/vuejs/language-tools/commits/v3.3.10/packages/tsc)

---
updated-dependencies:
- dependency-name: "@tsconfig/node24"
  dependency-version: 24.0.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: vue-tsc
  dependency-version: 3.3.10
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
…ependencies-eb533c92bf

chore(deps): bump python-dotenv from 1.2.2 to 1.2.3 in the python-dependencies group
…ntend/develop/npm-dependencies-e141f69f74

chore(deps): bump the npm-dependencies group in /app/frontend with 2 updates
Make stable publication fail closed on Trivy findings, bind release jobs
to protected environments, and correct the published architecture claim.
Add an executable workflow contract covering these boundaries.

Closes #802
Remove the build-only pip distribution and its embedded vendor SBOM from the final image. Normalize public runtime binary and library permissions for the non-root appuser and protect both invariants with mutation-resistant Dockerfile contract tests.\n\nCloses #804
Reject appended replacement stages that could reintroduce pip or override the non-root runtime user.\n\nRefs #804
fix(container): harden runtime image
fix(recording): prevent orphaned rotation processes
…ator

feat(twitch): coordinate persistent upstream leases
@Serph91P

Copy link
Copy Markdown
Owner Author

Promotion PR #809 is blocked by the independent exact-head technical gate for develop@5ec378f2300b77c6233bffbc7e0ef2487798e831 against main@5cba015cf5b741040c8f2b4ea45a67dc755fad42.

Reproducible in-scope P1 findings:

  1. app/services/recording/unified_recovery_service.py accesses the committed and detached upstream_lease.generation after the SessionLocal context closes. With expire_on_commit=True, eligible recovery reaches DetachedInstanceError and returns False after marking the previous recording stopped.
  2. Same-user, same-channel compatible Live starts are not idempotent during the reserved STARTING and playlist-readiness window. A duplicate request returns a conflict instead of preserving or joining the in-flight start.

The gate passed 64 focused tests, Ruff, diff hygiene and compilation, but those checks do not cover these two reproduced acceptance failures.

main remains unchanged and PR #809 remains Draft and unmerged. Issue #783 is reopened because both findings violate its accepted recovery-fencing and same-user idempotency requirements. No additional remediation worker is being started in this chain because its 90-minute execution budget is exhausted.

@Serph91P
Serph91P deployed to development-release August 22, 2026 09:34 — with GitHub Actions Active
@Serph91P
Serph91P deployed to development-release August 22, 2026 09:39 — with GitHub Actions Active
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