chore(release): graduate from beta prereleases to stable 0.1.0

[ajGingrich]

Summary

Graduates the project from beta prereleases to its first stable 0.1.0 release: removes all beta-prerelease wiring from the release process and user-facing docs, and pins the first stable version via a one-time Release-As: 0.1.0 commit footer.

Release version graduation

• commit footer — the graduating commit carries a Release-As: 0.1.0 footer, which tells release-please to open the next release PR as 0.1.0. This is a one-time override embedded in history, so there is no persistent config field to remove afterward. The branch is kept to a single commit so the footer survives the squash merge intact (squash_merge_commit_message is COMMIT_MESSAGES).
• release-please-config.json — remove the prerelease fields (versioning, prerelease, prerelease-type) so releases are no longer cut as prereleases.
• .github/workflows/release.yml — drop the beta/latest dist-tag conditional; publish directly to the default latest tag. The release-pipeline structure is otherwise unchanged: test/lint run on every PR and push to main, and the release workflow re-runs them as a final check (gated on release_created) before publish.

Documentation

• README.md — remove the status-beta badge, the pre-1.0 active-development notice, and the beta install warning; install via npm install redis-vl. Also correct the Node version badge (>=24.0.0 → >=22.0.0) to match engines.node and the CI test matrix.
• website/docs/intro.md — remove the pre-1.0 beta warning and the @beta install tag.

Intentionally left alone

• package.json, package-lock.json, and .release-please-manifest.json still read 0.1.0-beta.2. release-please bumps these itself in the release PR; with the Release-As: 0.1.0 footer they become 0.1.0. Hand-editing them would desync release-please's state tracking.
• The beta/BETA references in hybrid search (src/query/hybrid.ts, hybrid-search.md, tests) are the LINEAR combine weight parameter, unrelated to release status.

Important

Merge this PR with a single commit so the Release-As: 0.1.0 footer reaches main. The branch is already squashed to one commit; keep it that way at merge time.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Prepares the repository for its first stable v1.0.0 release by removing beta/prerelease-oriented release automation and updating user-facing installation docs to point at the stable npm package.

Changes:

• Pin the next release to 1.0.0 via release-as in release-please configuration.
• Simplify the release workflow to publish to npm without prerelease dist-tag branching.
• Update README + docs installation instructions to remove @beta and beta warning language.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
website/docs/intro.md	Removes pre-1.0 warning and updates install instructions to npm install redis-vl.
release-please-config.json	Switches from prerelease config fields to release-as: "1.0.0" to pin the first stable release.
README.md	Removes beta/status messaging and updates npm install command to the stable package.
.github/workflows/release.yml	Removes prerelease dist-tag selection and publishes to npm’s default latest tag.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bff6087618

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.