Skip to content

Conversation

@jackkoenig
Copy link
Contributor

Type of Improvement

  • Documentation or website-related

Desired Merge Strategy

  • Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

  • Did you add the appropriate labels? (Select the most appropriate one based on the "Type of Improvement")
  • Did you mark the proper milestone (Bug fix: 3.6.x, 5.x, or 6.x depending on impact, API modification or big change: 7.0)?
  • Did you review?
  • Did you check whether all relevant Contributor checkboxes have been checked?
  • Did you do one of the following when ready to merge:
    • Squash: You/ the contributor Enable auto-merge (squash) and clean up the commit message.
    • Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

@jackkoenig jackkoenig added the Documentation Only changing documentation label Oct 28, 2025
This is recommended by all documentation so we should follow the best
practice. Also use npm ci instead of npm install.
@jackkoenig jackkoenig merged commit 6c8d9d8 into main Oct 28, 2025
16 checks passed
@jackkoenig jackkoenig deleted the jackkoenig/update-website-deps branch October 28, 2025 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Only changing documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants