Conversation
* fix: harden agent integration checks * fix: require preload library before codex wrapper * fix: make codex wrapper setup idempotent * test: handle macos codex path canonicalization * docs: align platform integration behavior --------- Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
* docs: refresh rampart landing page * docs: deepen landing page SEO and visuals * docs: overhaul landing page hero and sections * docs: replace generated feature cards with product mechanics * docs: soften landing page origin note --------- Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
* fix: preserve modified built-in policy profiles * fix: clarify built-in policy drift detection --------- Co-authored-by: clap [bot] <clap@rampart.sh>
* harden openclaw approval handling * test: isolate proxy HOME state * fix: make allow-always writeback more robust on windows --------- Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
* release: v0.9.20 (#277) * fix: harden agent integration checks (#261) * fix: harden agent integration checks * fix: require preload library before codex wrapper * fix: make codex wrapper setup idempotent * test: handle macos codex path canonicalization * docs: align platform integration behavior --------- Co-authored-by: clap [bot] <clap@rampart.sh> * docs: polish integration platform guidance (#262) Co-authored-by: clap [bot] <clap@rampart.sh> * chore: prepare v0.9.19 release notes (#263) Co-authored-by: clap [bot] <clap@rampart.sh> * docs: refresh rampart landing page (#265) * docs: refresh rampart landing page * docs: deepen landing page SEO and visuals * docs: overhaul landing page hero and sections * docs: replace generated feature cards with product mechanics * docs: soften landing page origin note --------- Co-authored-by: clap [bot] <clap@rampart.sh> * docs: update deployed landing page source on staging (#269) Co-authored-by: clap [bot] <clap@rampart.sh> * docs: polish rampart landing page (#270) Co-authored-by: clap [bot] <clap@rampart.sh> * fix: preserve modified built-in policy profiles (#273) * fix: preserve modified built-in policy profiles * fix: clarify built-in policy drift detection --------- Co-authored-by: clap [bot] <clap@rampart.sh> * fix: harden OpenClaw approval fallback behavior (#275) * harden openclaw approval handling * test: isolate proxy HOME state * fix: make allow-always writeback more robust on windows --------- Co-authored-by: clap [bot] <clap@rampart.sh> * docs: tighten README and landing page voice (#274) Co-authored-by: clap [bot] <clap@rampart.sh> * chore: prepare v0.9.20 release notes (#276) Co-authored-by: clap [bot] <clap@rampart.sh> * docs: sync deployed landing page source with canonical page --------- Co-authored-by: clap [bot] <clap@rampart.sh> * fix: tighten openclaw setup trust signals * test: cover openclaw plugin doctor warnings * fix: tighten trust signals and self-mod policy * docs: align OpenClaw approval guide * docs: tidy support matrix placement --------- Co-authored-by: clap [bot] <clap@rampart.sh>
Co-authored-by: clap [bot] <clap@rampart.sh>
# Conflicts: # CHANGELOG.md # internal/plugin/openclaw/package.json
* ci: migrate workflows to Node 24-safe actions * fix: harden cli config resolution and hook failure handling * test: harden config parsing and ask-failure regressions * docs: polish config semantics and api override flows * fix: finalize rc hardening and release polish --------- Co-authored-by: clap [bot] <clap@rampart.sh>
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
1 participant
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.
Summary
Promote the current
stagingline tomainfor thev0.9.22release.This includes the recent release-hardening work plus the accumulated staging changes since
v0.9.20, including:Validation
CI / PR checks
Post-merge staging validation
go test ./... -count=1on mergedstagingfrom the actual staging worktreerampart-serverestarted onto the new binary and smoke-checked (status,doctor, pending/config behavior)trevors-macbook-pro(claptest) updated to latest staging buildgo test ./... -count=1passed on macOSdoctor,status, malformed-config behavior)Notes
I still think a short
v0.9.22-rc.1soak is the cautious move before merging this PR, because this line touches approval semantics, config resolution, and release workflow behavior.