Repository navigation
Release 2.0.1: personnel data authorization fixes - #35
Merged
Merged
Conversation
Signed-off-by: Patrick Schiller <p@trickschiller.de>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Signed-off-by: Patrick Schiller <p@trickschiller.de>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release OpenClockwork 2.0.1 with the personnel, leave and attendance read-authorization fixes from #34. Pin matching API/web images and update version metadata, the generated API artifacts, current installation examples and curated upgrade notes. The update adds no database migration from 2.0.0.
Custom clients must handle authenticated, scoped reads and use the minimal employee directory for substitute/project selectors. Security advisory: GHSA-4f2x-4pf8-wwx6 (publication follows successful artifact release).
Validation: regenerated OpenAPI/client,
RELEASE_TAG=v2.0.1 pnpm release:verify-tag, independent metadata/diff review, and full GitHub CI including API-E2E, database-upgrade and DCO. Publication uses the annotated v2.0.1 tag on the green main merge commit and the existing verify → GHCR images → GitHub Release workflow.