Repository navigation
Release v0.1.0 - #5
Merged
Merged
Conversation
Add persistent group ACLs, owner sharing controls, structured privilege errors, lossless bounded report projections and corrected custom timezone handling. Evaluate sync state tokens atomically in DAV conditions and avoid loading content for token-only properties. Preserve native client fixture bytes, record verified RFC corrections, and make host/container executable archives reproducible. Validation: Java 25.0.4.1; 123 unit and 125 PostgreSQL/HTTP integration tests passed without skips, including real Keycloak and Thunderbird/python-caldav cross-client operations. SpotBugs reported zero findings. Date-based HTTP conditions are being completed in the next increment.
Expose consistent Last-Modified and DAV getlastmodified metadata, evaluate date preconditions after current-state locking, and preserve ETag precedence and unchanged-byte dates. Use established HTTP-date parsing with strict obsolete-format checks, commit-ordered database wall-clock timestamps, and a Servlet emission boundary that prevents duplicate MVC condition evaluation. Validation: clean verify passed 149 unit and 134 PostgreSQL/HTTP integration tests without skips, including real Keycloak and independent Thunderbird/python-caldav round trips. SpotBugs reported zero findings. Independent host/container JARs match byte for byte.
Exercise real-browser group sharing, CSRF rejection, single-use recovery, local and federated HTTPS restoration, and a bounded independent-client workload. Require matching host/container JARs and install the exact pinned Temurin toolchain without unsupported four-part setup-java version parsing. Retain failure diagnostics and prevent token expiry from masquerading as restore revocation. The final runtime passed 149 unit and 134 integration tests; final packaged browser and workload profiles are running separately and are not represented as passed by this commit.
Make python-caldav expansion explicit in the bounded workload so the asserted dataset remains220 authoritative resources. Record the completed final runtime test, artifact and advisory evidence separately from packaged profiles still being qualified.
Keep recovery and OIDC browser assertions limited to the configured origin/root path, no fragment, and either no query or one empty continue parameter. Verify the authenticated account page after redirect. This corrects fixture expectations for Spring saved requests without changing application behavior.
Connect the standards and security matrices to executed runtime, desktop-client, browser, Keycloak, restoration and workload evidence. Preserve failed attempts and exact artifact/version/license inventories, document deployment and recovery policy, and distinguish the unresolved owner license decision and unexecuted external reviews from completed engineering checks.
Persist immutable sync history and resumable collection-scoped watermarks, separate metadata and selected property reads, and bound report construction before serialization. Preserve XML language context and per-member report errors. Unify namespace preflight and XML character validation, reconcile large sharing sets atomically, and extend fail-closed recovery through V13. Enable the constrained sync Depth 1 default with a strict override.
Exercise paged capacity and concurrent property/sharing workloads through real HTTPS, record effective sync configuration and running heap limits, and retain current-source qualification separately from historical evidence. Extend native/Python same-resource recurrence checks, restoration refresh/session assertions, license artifact inspection and fail-closed container OS advisory scanning in required CI entry points.
Charge existing components against the shared work budget and cap actual calendar-query matches separately, retaining recurrence generation and free-busy result guards. Cover 10037-resource selective queries and low-limit event, task, property and alarm cases. Set proxy and selective-client read deadlines from measured large-query durations while keeping other request and authentication deadlines unchanged. Require a clean full CI verification.
Record configured health deadlines, the last five sanitized probe attempts and bounded startup and migration milestones. Preserve credential redaction and exclude arbitrary request logs without changing production health timing.
Connect the conformance, security, licensing, client and operations documentation to source 47b3543 and verified CI/local artifacts. Retain the original failures and their scope, final default/strict client results, 10037-resource pagination and selective-query measurements, 12500-grant management, and both local and federated restoration. Preserve historical evidence and record unexecuted GUI, physical-authenticator and optional-feed checks honestly.
Close IV-CAL-01 with nonzero BYDAY ordinals, shared duration alternatives and exact ASCII calendar boundaries. Preserve BOM and raw bytes, and verify rejected creation and conditional replacement leave resource/history/revision/sync state unchanged.
Close IV-AUTH-01 without accepting nonempty or duplicate credentials. Keep the converter scoped to token and revocation endpoints, and verify real HTTP refresh/error/rotation behavior and rejected-request grant preservation.
Complete and publish CalDAV Server 0.0.1 from verified artifacts
Qualify restoration from source-free deployment bundles
Use readable candidate tags and focused product documentation
Resume draft releases without changing qualified artifacts
albert-gee
marked this pull request as ready for review
November 2, 2026 03:11
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.
Prepare the public v0.1.0 release with Maven-authoritative versioning, source-bound artifacts, automatic developer Docker metadata, and exact staged-asset promotion.
Public-tree cleanup removes raw logs, screenshots, compressed GUI captures, duplicate execution records and obsolete agent instructions. Exact historical records are preserved in the external audit archive and existing Git history. Concise version-specific qualification receipts remain; maintained test fixtures and publication gates are intact. README, release notes, operating documentation and website handoff are publication-ready, with no unnecessary workstation details. The release description is 208 words and is rendered from the exact qualified source.
Application source, dependencies, migrations, Dockerfile, Compose runtime inputs and application fixtures are byte-identical to the previously qualified implementation. Native-client qualification remains bound to the same JAR checksum and runtime inputs; no GUI requalification is needed for this documentation/evidence cleanup. Release regressions (29), distribution tests (11), documentation links and the actual client-receipt gate pass locally.
Cleanup head:
d3905031364f0d3b202a49604079f01e8d6fd00f. Required push CI and PR CI are running.The owner has authorized integration and publication after all acceptance gates pass. Squash this exact reviewed head as
Release v0.1.0, preserve the release branch, verify the two-commit main history and identical tree, then qualify the final squash SHA. Use the existing explicit staging/publication workflow and inspect complete deployment/anonymous acceptance before safe retirement or supersession of v0.0.1. No website changes are included.