Add clarifying details for private module registry version attribute commit-sha

[tism]

What

Update the default and description for the commit-sha attribute when creating a non-VCS connected private registry module version

Why

Clarifies what is needed by the API

Screenshots

N/A

---

Merge Checklist

If items do not apply to your changes, add (N/A) and mark them as complete.

Pull Request

• One or more labels describe the type of change (e.g. clarification) and associated product (e.g. HCP Terraform ).
• Description links to related pull requests or issues, if any.

Content

• Redirects have been added to website/redirects.js for moved, renamed, or deleted pages. (N/A)
• API documentation and the API Changelog have been updated. (N/A)
• Links to related content where appropriate (e.g., API endpoints, permissions, etc.). (N/A)
• Pages with related content are updated and link to this content when appropriate. (N/A)
• Sidebar navigation files have been updated for added, deleted, reordered, or renamed pages. (N/A)
• New pages have metadata (page name and description) at the top. (N/A)
• New images are 2048 px wide. They have HashiCorp standard annotation color (#F92672) and format (rectangle with rounded corners), blurred sensitive details (e.g. credentials, usernames, user icons), and descriptive alt text in the markdown for accessibility. (N/A)
• New code blocks have the correct syntax and line breaks to eliminate horizontal scroll bars. (N/A)
• UI elements (button names, page names, etc.) are bolded. (N/A)
• The Vercel website preview successfully deployed.

Reviews

• I or someone else reviewed the content for technical accuracy.
• I or someone else reviewed the content for typos, punctuation, spelling, and grammar.

[vercel]

@tism is attempting to deploy a commit to the HashiCorp Team on Vercel.

A member of the Team first needs to authorize it.