chore: say teams in the README, and sync the lockfile workspace versions - #125
Merged
Conversation
The README's v1.0.0 priorities listed Credential Sharing as covering ".env, Doppler, Railway variables, and GitHub Secrets" -- the same drift just fixed on the marketing page in #123. End-to-end-encrypted team vaults shipped on 2026-07-13 and sh1pt landed as a provider on 07-30, so the highest-traffic surface in the repo still told readers teams did not exist. Separately, packages/cli and plugins/credential-sharing were bumped to 0.1.1 in their package.json without the lockfile following, so it still recorded 0.1.0 for both. Reconciled with `npm install --package-lock-only`; the diff is those two version fields and nothing else. This was cosmetic rather than breaking -- `npm ci` tolerated the mismatch, which is why CI never caught it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
ThreatCrush Security Scan55 finding(s) HIGH/CRITICAL: 30 | MEDIUM: 25
…and 5 more. Full results in the Security tab. Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Two pieces of housekeeping left over from #123 and #124.
README
README.md:119listed Credential Sharing as covering ".env, Doppler, Railway variables, and GitHub Secrets" — the identical drift #123 just fixed on the marketing page. End-to-end-encrypted team vaults shipped 2026-07-13 and sh1pt landed as a provider 07-30, so the repo's front page still told visitors teams did not exist. Same sentence, now accurate.Lockfile
packages/cliandplugins/credential-sharingwere bumped to0.1.1in theirpackage.jsonwithout the lockfile following — it still recorded0.1.0for both. This surfaced during #123, where I reverted it to keep that PR focused.Reconciled with
npm install --package-lock-only. The entire diff:No dependency churn.
Worth being clear that this was cosmetic, not breaking:
npm citolerated the mismatch, which is why CI stayed green through it. It is hygiene so the lock tells the truth about what is in the tree, not a fix for a live failure.Verification
npm ci— exit 0 against the reconciled lock, and it does not re-modify the lockfile afterward.🤖 Generated with Claude Code