Skip to content
Discussion options

You must be logged in to vote
Admin verified this answer by prplwtf Jun 4, 2026

This is related to a current bug that doesn't unlock Blueprint's lockfile whenever you run into an issue during extension installation. For now, you can just run blueprint -unlock without any arguments to get it to work.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@prplwtf
Comment options

prplwtf Jun 4, 2026
Maintainer Sponsor

Answer verified by Admin Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants