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

Update Vitepress version #12400

Merged
merged 1 commit into from
Feb 9, 2025
Merged

Conversation

hamishwillee
Copy link
Contributor

This updates the package.json for the docs build.

Specifically it adds license info that otherwise gives build warning. But I also updated description, version, repo, and the Vitepress version.

We should probably move this file into docs to improve build "hygiene", but that would require I update the build actions too, and I don't have time.

Note, I was here to update the instructions to remove gstreamer dependencies, but since the install docs refer to the current release build, and that still requires them, have not done so.

@HTRamsey
Copy link
Collaborator

HTRamsey commented Feb 6, 2025

Could you add package-lock.json to the paths in the docs_deploy.yml workflow so it'll run the CI test?

@HTRamsey HTRamsey force-pushed the package_file_update branch from 3d44e1e to 0c00904 Compare February 9, 2025 07:20
@HTRamsey HTRamsey merged commit 3b56d05 into mavlink:master Feb 9, 2025
2 checks passed
@hamishwillee
Copy link
Contributor Author

Could you add package-lock.json to the paths in the docs_deploy.yml workflow so it'll run the CI test?

@HTRamsey I only work 2 days a week, so missed this. At some point yes. It is not currently a priority for me.

@HTRamsey
Copy link
Collaborator

No worries I took care of it

@hamishwillee hamishwillee deleted the package_file_update branch February 11, 2025 22:24
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