Skip to content

Conversation

hooray
Copy link
Contributor

@hooray hooray commented Sep 16, 2025

πŸ”— Linked issue

❓ Type of change

  • πŸ“– Documentation (updates to the documentation, readme or JSdoc annotations)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ 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

πŸ“Έ Screenshots (if appropriate)

πŸ“ Checklist

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

@sadeghbarati sadeghbarati changed the base branch from dev to v4-docs September 16, 2025 18:37
@sadeghbarati
Copy link
Collaborator

sadeghbarati commented Sep 16, 2025

Thanks, changed the base branch to v4-docs, cause we are working on that branch

@sadeghbarati sadeghbarati merged commit baf63ac into unovue:v4-docs Sep 16, 2025
2 checks passed
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