feat(object-storage)!: rename s3 command to object-storage (aliases oss, d4)#53
Merged
Conversation
…ss, d4) Renames the `s3` command to `object-storage` to avoid the naming conflict with AWS S3. Adds `oss` and `d4` as aliases. BREAKING CHANGE: `verda s3 ...` no longer works. Use `verda object-storage ...` (or the `oss` / `d4` aliases) instead. Scope: - Folder/package renamed s3/ -> objectstorage/ (Go package `objectstorage`, constructor `NewCmdObjectStorage`); subcommand logic and tests unchanged. - Command `Use: "object-storage"`, `Aliases: [oss, d4]`; root help and the credential-skip check updated accordingly. - All `verda s3 ...` / `--agent s3 ...` invocations in help, examples, README, per-command CLAUDE.md, and embedded skills rewritten to `verda object-storage ...`; aliases documented in the skills. - Stale `s3` cross-references in the sibling `registry` package docs and comments fixed (incl. the user-facing registry README copy-wizard note that pointed at the now-removed `s3 cp`). Intentionally preserved (non-breaking): the `s3://` URI scheme and the `verda_s3_` credential keys, so existing credentials and paths keep working. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Addresses two standard-library vulnerabilities flagged by govulncheck, both fixed in go1.25.11: - GO-2026-5039: unescaped inputs in net/textproto errors (reached via util.debugTransport.RoundTrip -> io.ReadAll -> textproto.Reader.ReadMIMEHeader) - GO-2026-5037: inefficient candidate hostname parsing in crypto/x509 (reached via registry.httpLister.Ping and util.ClassifyError) CI installs the toolchain from go-version-file: go.mod, so bumping the `go` directive is sufficient. Verified clean with `GOTOOLCHAIN=go1.25.11 govulncheck ./...` -> No vulnerabilities found. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
Renames the top-level
s3command toobject-storageto avoid the naming conflict with AWS S3, and addsossandd4as aliases.Warning
Breaking change.
verda s3 …no longer works. Users must switch toverda object-storage …(or theoss/d4aliases). Stored credentials ands3://paths are unchanged, so no re-configuration is needed.What changed
s3/→objectstorage/(Go packageobjectstorage, constructorNewCmdObjectStorage). Subcommand logic and tests are unchanged — only the mechanical package rename.Use: "object-storage",Aliases: ["oss", "d4"]. Root help grouping and theskipCredentialResolutioncheck updated to match.verda s3 …,verda --agent s3 …, and bare`s3 <verb>`references rewritten toobject-storageacross command help, READMEs, per-commandCLAUDE.md, and both embedded skill files. Theoss/d4aliases are documented in the skills.s3cross-references in docs/comments now that the sibling command is renamed, including the user-facingregistry/README.mdcopy-wizard note that pointed at the now-removeds3 cp.Intentionally preserved (non-breaking)
s3://URI scheme in command arguments (industry-standard scheme identifier, not the product name).verda_s3_credential keys in~/.verda/credentials(also read byregistry), so existing users' credentials keep resolving.Verification
verda object-storage --help,verda oss …,verda d4 …all resolve; bareverda s3correctly returnsunknown command "s3".make build,make test(22 packages, no failures), andmake lint(0 issues) all pass; pre-commit hooks green.🤖 Generated with Claude Code