Skip to content

[DOCS] Changing 1.0 to 1.0.0 #3486

Merged
whysosaket merged 1 commit intomainfrom
user/parshva/docs_fix_1.0
Sep 20, 2025
Merged

[DOCS] Changing 1.0 to 1.0.0 #3486
whysosaket merged 1 commit intomainfrom
user/parshva/docs_fix_1.0

Conversation

@parshvadaftari
Copy link
Copy Markdown
Contributor

Description

Docs change from 1.0beta to 1.0.0beta

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Maintainer Checklist

  • closes #xxxx (Replace xxxx with the GitHub issue number)
  • Made sure Checks passed

@whysosaket whysosaket merged commit 88ae952 into main Sep 20, 2025
4 of 5 checks passed
@parshvadaftari parshvadaftari deleted the user/parshva/docs_fix_1.0 branch September 26, 2025 11:29
jamebobob pushed a commit to jamebobob/mem0-vigil-recall that referenced this pull request Mar 29, 2026
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