You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The release workflows for #99 and #100 failed to push their version tags because their fork-headed pull_request events received read-only tokens. The latest published version remains v0.22.1.
Add a short README note describing the accumulated v0.23.0 changes. Merging this feature branch triggers a minor release from current main, including #98 (BED-10432), #99 (BED-10447), and #100 (BED-10454).
The identical commit was pushed first to the fork and then to the same-named upstream branch. This PR uses the upstream branch as its head so the existing release workflow can receive its declared write permissions.
Validation: git diff --check passed; verified both remote branch SHAs match. Documentation-only recovery change; implementation checks are recorded in the original PRs. After merge, verify tag v0.23.0, PyPI publication, and scheduler/CLI container publication.
Summary by CodeRabbit
Documentation
Added Version 0.23.0 release notes covering enterprise OIDC providers and external identities, enterprise installation metadata, and fixes to Tier Zero role matching and expired-token filtering.
No actionable comments were generated in the recent review.
Walkthrough
README.md adds a Version 0.23.0 release note. It summarizes changes related to enterprise OIDC providers, external identities, enterprise installation metadata, Tier Zero role matching, and expired-token filtering.
Changes
Version 0.23.0 release note
Layer / File(s)
Summary
Document release changes README.md
Adds a Version 0.23.0 heading and summarizes the release changes.
This adds the v0.23.0 release note without changing application behavior. No merge-blocking risk was identified.
Architecture risk: Low · up to 7bc4d
The change affects 1 system.
Changed systems:README.md
Architecture concerns
No architecture-level concerns identified.
Review details
Systems and components
observed — README.md (service) was modified; 1 changed file maps to changed impact.
Before / after behavior
observed — Modified behavior in README.md: Added the Version 0.23.0 release heading and a summary of the release’s OIDC, external identity, enterprise installation metadata, Tier Zero role-matching, and expired-token-filtering changes.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title identifies the v0.23.0 release recovery, which is the stated purpose of the README change.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
A rabbit reads the release note bright, OIDC hops into the light. External identities join the trail, Enterprise details follow without fail. Tier Zero gets its match just right, Expired tokens leave the site.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: ebd0519d-38cc-4b0b-a795-3dd276df8e00
Commits
Reviewing files that changed from the base of the PR and between 95ce81f and 7bc4d5a.
Files selected for processing: 1
README.md
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflows for #99 and #100 failed to push their version tags because their fork-headed pull_request events received read-only tokens. The latest published version remains v0.22.1.
Add a short README note describing the accumulated v0.23.0 changes. Merging this feature branch triggers a minor release from current main, including #98 (BED-10432), #99 (BED-10447), and #100 (BED-10454).
The identical commit was pushed first to the fork and then to the same-named upstream branch. This PR uses the upstream branch as its head so the existing release workflow can receive its declared write permissions.
Validation: git diff --check passed; verified both remote branch SHAs match. Documentation-only recovery change; implementation checks are recorded in the original PRs. After merge, verify tag v0.23.0, PyPI publication, and scheduler/CLI container publication.
Summary by CodeRabbit