Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: fix legacy docs build (attempt 2) #7149

Merged
merged 6 commits into from
May 10, 2024

Conversation

lsliwaradioluz
Copy link
Collaborator

πŸ”— 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

πŸ“ Checklist

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

@lsliwaradioluz lsliwaradioluz requested a review from a team as a code owner May 10, 2024 17:24
Copy link

changeset-bot bot commented May 10, 2024

⚠️ No Changeset found

Latest commit: bb0c23b

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.

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

@lsliwaradioluz lsliwaradioluz changed the base branch from main to legacy May 10, 2024 17:24
@github-actions github-actions bot deployed to production May 10, 2024 17:39 Active
@lsliwaradioluz lsliwaradioluz merged commit 6625358 into legacy May 10, 2024
4 checks passed
@lsliwaradioluz lsliwaradioluz deleted the chore/fix-legacy-docs-build-2 branch May 10, 2024 17:42
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.

1 participant