Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Parse "../package.json" as app version

See original GitHub issue

The package.version field of tauri.conf.json supports using "../package.json" as a value, so they share the same version. From what I can tell, this package doesn’t check if that’s the case, leading to an error in my app’s workflow:

   Compiling note-boi v0.1.0 (/Users/runner/work/note-boi/note-boi/src-tauri)
    Finished release [optimized] target(s) in 6m 35s
    Bundling NoteBoi.app
    Bundling "/Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/dmg/NoteBoi_0.1.3_x64.dmg"
info: running bundle_dmg.sh
    Bundling "/Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app.tar.gz"
        /Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app
        /Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/dmg/NoteBoi_0.1.3_x64.dmg
        /Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app.tar.gz (updater)
    Finished 3 bundles at:
[Signed] 1 updater archive at:
        /Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app.tar.gz.sig
Artifacts: /Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app,/Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app.tar.gz,/Users/runner/work/note-boi/note-boi/src-tauri/target/release/bundle/macos/NoteBoi.app.tar.gz.sig.
Couldn't find release with tag v../package.json. Creating one.
Error: Validation Failed: {"resource":"Release","code":"custom","field":"tag_name","message":"tag_name is not a valid tag"}, {"resource":"Release","code":"custom","field":"tag_name","message":"tag_name is not well-formed"}, {"resource":"Release","code":"custom","message":"Published releases must have a valid tag"}

Have I made a mistake somewhere or is this a feature that needs to be added?

Relevant YAML file.

Issue Analytics

State:
Created a year ago
Comments:5 (3 by maintainers)

Top GitHub Comments

4reactions

FabianLarscommented, Apr 30, 2022

Have I made a mistake somewhere or is this a feature that needs to be added?

You’re right, it’s not handled correctly. Thx for the report.

0reactions

nwesterhausencommented, Jun 16, 2022

I have had it working since the merge by using the commit hash: ‘@<hash>’

I was not have success leaving it at ‘@v0’

Quick update: After trying ‘@dev’ I have had success.

On Wed, Jun 15, 2022, 4:28 AM Fabian-Lars @.***> wrote:

As long as you use @.*** or @dev it should pull the latest version automatically. And yes, it’s supposedly fixed now, though I didn’t test it myself yet tbh.

— Reply to this email directly, view it on GitHub https://github.com/tauri-apps/tauri-action/issues/262#issuecomment-1156159644, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARVYRMB7PBYSM7KX5QT3ZLVPGH3PANCNFSM5UY4ZL7A . You are receiving this because you are subscribed to this thread.Message ID: @.***>