Repository navigation
Correct RowSafe standalone backup account requirements - #87
Merged
Ritual-Dev-Git merged 2 commits intoOct 17, 2026
Merged
Conversation
divyanshujethi
added a commit
that referenced
this pull request
Oct 17, 2026
…in community hall of fame
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
2 participants
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.
Corrects the existing RowSafe description for released v0.10.19. The Linux PostgreSQL agent can now run backups to the user’s own storage, Marks and weekly restore tests without a RowSafe account. Dashboard, alerts, Rewind and managed cloud remain account features. The direct PostgreSQL CLI/local MCP remains account-free.
Evidence: v0.10.19 release, pinned README, and embedded local control plane.
This updates an existing entry and its generated description copies, without changing links, categories, counts or unrelated entries. Build timestamp churn was excluded.
Validation: on current upstream main, schema validation passed for 533 entries; site/API/README/SEO build, all 85 tests, Biome format and git diff --check passed. Before rebasing onto current main, the earlier baseline initially reported 56/57 tests passing and a diagnostic rerun without code changes passed 57/57; the cause was not established. The required standard link audit checked 533 endpoints: 508 active/reachable (95.3%), 1 bot/CDN challenge, 162 redirects and 25 degraded/dead endpoints elsewhere in the catalog; RowSafe returned HTTP 200 after redirecting to https://rowsafe.sh/. Audit telemetry and unrelated build timestamp churn were excluded from this metadata-only change. No runtime or database test is claimed.
Disclosure: submitted on behalf of Emad Alharbi, Founder of RowSafe, with AI assistance.
PR Integrity Gate initially found the description was 310 characters, exceeding its 300-character maximum. The description is now 262 characters; the supported PR validator with GITHUB_BASE_REF=main passes (117 CLI entries, zero duplicate collisions), along with full schema validation, build, all 85 tests, Biome format and diff checks. Only the existing description and generated copies changed.