Skip to content

Conversation

@ejscribner
Copy link
Contributor

Fixes # (issue)

@vercel
Copy link

vercel bot commented Jun 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
langchainjs-docs ✅ Ready (Inspect) Visit Preview Jun 11, 2025 2:32pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
langchainjs-api-refs ⬜️ Ignored (Inspect) Jun 11, 2025 2:32pm

@christian-bromann
Copy link
Member

@ejscribner thanks for your contribution 🎉 are you still interested getting this landed in LangChain? Anything we can do to support?

@ejscribner
Copy link
Contributor Author

Thanks for the response! Yes, we definitely will want to land this, but it depends on some other work so I've left it as a draft for now. Hoping to have it ready for review soon 🙂

@ejscribner ejscribner marked this pull request as ready for review October 21, 2025 16:28
@ejscribner ejscribner marked this pull request as draft October 21, 2025 16:38
@changeset-bot
Copy link

changeset-bot bot commented Oct 21, 2025

⚠️ No Changeset found

Latest commit: 3392e60

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ejscribner ejscribner marked this pull request as ready for review October 22, 2025 23:23
@ejscribner
Copy link
Contributor Author

Hey @christian-bromann, we're ready to release this now that Couchbase 8.0 is released. I've added docs as well: langchain-ai/docs#1079.

Not sure if we need a changeset here or not, but let me know if I need to do anything for that. Thanks for your patience and help with this one!

@christian-bromann
Copy link
Member

@ejscribner no problem, thanks for putting this together. Let me check in with the team again and get back to you this week. In the meantime, mind to take a look at this small linting errors?

lnhsingh added a commit to langchain-ai/docs that referenced this pull request Nov 6, 2025
…factor existing Couchbase docs (#1079)

## Overview
- Adds a new page illustrating usage for new CouchbaseQueryVectorStore
(langchain-ai/langchainjs#8333)
- Refactors existing page path to ensure distinction between
couchbase_search and couchbase_query
- Adjusts some language for clarity

## Type of change

**Type:** New documentation page

## Related issues/PRs
<!-- 
Link to related issues, feature PRs, or discussions (if applicable)

To automatically close an issue when this PR is merged, use closing
keywords:
- "closes #123" or "fixes #123" or "resolves #123"

For regular references without auto-closing, just use:
- "#123" or "See issue #123"

Examples:
- closes #456 (will auto-close issue #456 when PR is merged)
- See #789 for context (will reference but not auto-close issue #789)
-->
- GitHub issue:
- Feature PR: langchain-ai/langchainjs#8333

<!-- For LangChain employees, if applicable: -->
- Linear issue:
- Slack thread:

## Checklist
<!-- Put an 'x' in all boxes that apply -->
- [x] I have read the [contributing guidelines](README.md)
- [x] I have tested my changes locally using `docs dev`
- [x] All code examples have been tested and work correctly
- [x] I have used **root relative** paths for internal links
- [x] I have updated navigation in `src/docs.json` if needed
- I have gotten approval from the relevant reviewers

## Additional notes
<!-- Any other information that would be helpful for reviewers -->

---------

Co-authored-by: Lauren Hirata Singh <[email protected]>
Co-authored-by: Mason Daugherty <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants