release: promote v1.0.0 to main - #375
Conversation
* Document v1 external readiness gates * Address v1 readiness review feedback
* chore(release): prepare v1.0.0 * docs: tighten v1 evidence boundaries * docs: bind attested counts to baseline
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 9 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (25)
Comment |
|
@coderabbitai review |
|
1 participant
Summary\n\nPromote the exact protected development head 3940383 to main for @lubab/miftah@1.0.0.\n\nThis promotion includes:\n- finalized 1.0.0 package and lockfile metadata plus changelog;\n- stable Semantic Versioning compatibility commitments;\n- the dependency security refresh from #373;\n- v1 readiness and evidence-boundary documentation;\n- all other user-visible changes accumulated on development since published v0.5.8.\n\n## Exact-head evidence\n\n- release preparation: #374\n- exact development push CI: https://github.com/mohanagy/miftah/actions/runs/31459111259\n- Linux quality, coverage, build, smoke, and package checks: passed\n- Node 20/22/24 across Ubuntu, macOS, and Windows: passed\n- npm audit production and full tree: zero known vulnerabilities\n\n## Evidence boundary\n\nThe 5/3/3 external counts and completed security report are recorded as maintainer attestation. The source participant records and report contents were not independently inspected in this release session; provider coverage, reviewer attribution, severity counts, remediation, and candidate-delta acceptance are not inferred.\n\n## Publication boundary\n\nAfter this PR is reviewed, passes exact-head protected CI, and merges, v1.0.0 will be released only from the exact current main commit. The GitHub Release must trigger protected OIDC publication; #39 remains open until registry provenance, fresh installation, and signatures are verified.\n\nRefs #39.