-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Labels
enhancementNew feature or requestNew feature or request
Description
It is not easy to identify the version of the used Logseq static build and the publish-spa version that was used during publication.
It would help a lot if (at least as a debug option) the version tag of publish-spa and the logseq static build is included either in the html source as metadata or in the SPA UI reachable over an about link in the help section.
Why is adding your own page not sufficient?
The purpose is to have a proof of the actual used version instead of the intended versions, to spot misconfiguration or failed attempts to update the code.
challenges
- The commandline command
logseq-publish-spahas no --version output option or drops it during execution - The command
logseq-publish-spahas no verbose option to dump the version of the static logseq build, you just rely on the given path.
If not available like suggested:
- how can the version be retrieved manually from the final SPA build or from the installed code?
- the actual state of the checkout (git status) is not enough, since the
yarn installdoes not offer useful output in his warnings. - the full (re-)install command I used was:
logseq % yarn install --frozen-lockfile && yarn gulp:build && clojure -M:cljs release publishing- Maybe there is a different syntax necessary to update properly
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request