chore: prepare v1.0.0-beta.1 release

[RentnerKev]

Summary

Final release gate for the first public Beta of RentnerProxy.

DO NOT execute this issue now.

Release Requirements

Before Beta 1:

• planned Beta feature issues complete or explicitly deferred
• Alpha 3 tester feedback triaged
• upgrade path verified
• upgrade compatibility matrix green
• backup/restore compatibility green
• security review complete
• no P0/P1 release blocker
• required CI checks green
• Production Smokes green
• long-running reliability test green
• scale/concurrency test green
• fresh install verified
• upgrade verified
• published image verified

Release

Target:

v1.0.0-beta.1

GitHub Release:

Pre-release

Container immutable tag:

ghcr.io/rentnerkev/rentnerproxy:v1.0.0-beta.1

Development/pre-release moving channel:

use current repository release policy.

Do NOT update stable-only channels unless current repository policy
explicitly says otherwise.

Feature Freeze

After Beta 1:

large new v1 features should generally stop.

Focus moves to:

• bugs
• compatibility
• performance
• stability
• tester feedback

Priority

P0 / final gate

Dependencies and sequencing

This is the final gate, not an instruction to implement or publish during roadmap setup.

• CrowdSec protection feat: integrate CrowdSec protection #64 (complete or explicitly deferred)
• Forward Auth access policies feat: add Forward Auth access policies #65 (complete or explicitly deferred)
• NPM importer feat: add Nginx Proxy Manager importer #66 (complete or explicitly deferred)
• Alpha-to-Beta upgrade hardening fix: harden alpha-to-beta upgrade path #67
• Release upgrade compatibility matrix test: add release upgrade compatibility matrix #68
• Long-running reliability test: add long-running runtime reliability tests #69
• Scale/concurrency coverage test: add proxy scale and concurrency coverage #70
• Backup/restore compatibility fix: harden backup and restore compatibility #71
• Final security review and blocker remediation security: complete v1 beta security review #72
• Alpha 3 feedback triage and blocker resolution fix: address v1.0.0-alpha.3 tester feedback #73
• Beta accessibility/UX review fix: complete beta accessibility and UX review #74

The existing release workflow selects the beta moving channel for a v1.0.0-beta.1 pre-release, alongside its immutable version tag; latest is reserved for stable releases. Verify that policy again at release time. Publication and published-image verification require a separately authorized release operation. Keep this issue OPEN during roadmap setup.

Acceptance Criteria

• Required linked Beta gates are complete; any planned feature deferral has an explicit rationale and no unresolved P0/P1 blocker remains.
• Exact release-candidate CI, Production Smokes, supported upgrade/restore matrix, soak and scale/concurrency results are green.
• Fresh installation, supported upgrades, release notes and feature-freeze boundaries are verified.
• During a separately authorized release: verify the immutable Beta image, moving beta tag, pre-release metadata and published artifacts before closing this gate.

Alpha 4 prerequisite

Alpha 4 precedes Beta 1. Require #85 and the Alpha 4 milestone as prerequisites, then verify Alpha 4 -> Beta 1 plus supported older paths. HTTP/3 origin support is owned by Alpha 4 #82 and must be regression-tested, not implemented anew as Beta scope. All actual Beta gates remain open.

[github-actions]

🔍 Similar issues found

This issue may overlap with existing reports. Please take a look at these related items.

Match	Issue	Status
Medium	#36 – chore: prepare v1.0.0-alpha.2 release	CLOSED · COMPLETED
Medium	#15 – chore: prepare v1.0.0-alpha.1 release	CLOSED · COMPLETED
Medium	#61 – chore: prepare v1.0.0-alpha.3 release	CLOSED · COMPLETED

This is an automated suggestion. This issue has not been closed automatically.