Skip to content

Conversation

HugoRCD
Copy link
Member

@HugoRCD HugoRCD commented Aug 21, 2025

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality)
  • ✨ New feature (a non-breaking change that adds functionality)
  • 🧹 Chore (updates to the build process or auxiliary tools and libraries)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

benjamincanac and others added 30 commits August 14, 2025 21:28
Co-authored-by: Jakub <[email protected]>
Co-authored-by: Benjamin Canac <[email protected]>
@benjamincanac benjamincanac changed the title feat(docs): add migration guide v3 to v4 docs(migration): add guide from v3 to v4 Aug 25, 2025
@benjamincanac benjamincanac added the documentation Improvements or additions to documentation label Aug 25, 2025
@benjamincanac benjamincanac changed the title docs(migration): add guide from v3 to v4 docs(migration): write guide from v3 to v4 Aug 27, 2025
@benjamincanac benjamincanac merged commit 1b2c2dd into v4 Aug 27, 2025
6 checks passed
@benjamincanac benjamincanac deleted the feat/migration-docs-v4 branch August 27, 2025 16:11
benjamincanac added a commit that referenced this pull request Sep 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation v4 #4488
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants