Publishing to a public github repo from a private repo - getting version "0.0.0.0"

[jpage4500]

I'm trying to publish to a public github repo from a private repo and running into an issue. The public repo is getting published to a release named "main" and not the version of the app I'm using.

My CI process updates the version in the jdeploy package.json file and I can see that working:

2026-03-10T18:12:40.2185366Z Updated package.json:
2026-03-10T18:12:40.2199010Z   "version": "1.0.436",
2026-03-10T18:12:40.2528777Z ##[group]Run shannah/jdeploy@master
2026-03-10T18:12:40.2529792Z   target_repository: jpage4500/HubitatDashboard
2026-03-10T18:12:40.2530128Z   deploy_target: github
2026-03-10T18:12:40.2530388Z   jdeploy_version: 6.0.19
2026-03-10T18:12:40.2531055Z   require_existing_jdeploy_tag: false
...
2026-03-10T18:12:40.2537480Z   VERSION: 1.0.436

Part of the CI build also creates a release in my private repo and that works too

But, the public repo ends up with only an updated 'main' release and the artifacts are all labeled "0.0.0.0"

see https://github.com/jpage4500/HubitatDashboard/releases

I'm just trying to figure out a nice and clean way to push new builds.. ideally with github actions doing all of the work and I just have to merge in a PR.

I'm happy to share my github actions scripts or build log if it'll help. I'm guessing that maybe this issue has to do with the fact that I'm publishing to another repo so hoping someone else has some tips & tricks I can use

[jpage4500]

job-logs2.txt

attaching the GA logs if it helps.. only errors I see are:

2026-03-10T18:12:40.2537480Z   VERSION: 1.0.436
2026-03-10T18:12:40.2537714Z ##[endgroup]
2026-03-10T18:12:40.2632870Z ##[group]Run REF_NAME="main"
2026-03-10T18:12:40.2633208Z �[36;1mREF_NAME="main"�[0m
2026-03-10T18:12:40.2633467Z �[36;1m�[0m
2026-03-10T18:12:40.2633900Z �[36;1m# Check if ref name contains only allowed characters (letters, digits, dash, underscore, dot)�[0m
2026-03-10T18:12:40.2634470Z �[36;1mif [[ ! "$REF_NAME" =~ ^[a-zA-Z0-9._-]+$ ]]; then�[0m
2026-03-10T18:12:40.2635186Z �[36;1m  echo "Branch/tag name '$REF_NAME' contains illegal characters. Only letters, digits, dash (-), underscore (_), and dot (.) are allowed."�[0m
2026-03-10T18:12:40.2635920Z �[36;1m  echo "Skipping action execution due to invalid ref name."�[0m
2026-03-10T18:12:40.2636378Z �[36;1m  echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m
2026-03-10T18:12:40.2636731Z �[36;1m  exit 0�[0m
2026-03-10T18:12:40.2636963Z �[36;1mfi�[0m
2026-03-10T18:12:40.2637188Z �[36;1m�[0m
2026-03-10T18:12:40.2637472Z �[36;1m# Check if ref name length exceeds 16 characters�[0m
2026-03-10T18:12:40.2637848Z �[36;1mif [[ ${#REF_NAME} -gt 16 ]]; then�[0m
2026-03-10T18:12:40.2638424Z �[36;1m  echo "Branch/tag name '$REF_NAME' is too long (${#REF_NAME} characters). Maximum allowed length is 16 characters."�[0m
2026-03-10T18:12:40.2639088Z �[36;1m  echo "Skipping action execution due to ref name length limit."�[0m
2026-03-10T18:12:40.2639561Z �[36;1m  echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m
2026-03-10T18:12:40.2639919Z �[36;1m  exit 0�[0m
2026-03-10T18:12:40.2640161Z �[36;1mfi�[0m
2026-03-10T18:12:40.2640380Z �[36;1m�[0m
2026-03-10T18:12:40.2640646Z �[36;1mecho "Branch/tag name '$REF_NAME' is valid."�[0m
2026-03-10T18:12:40.2641053Z �[36;1mecho "JDEPLOY_SKIP_EXECUTION=false" >> $GITHUB_ENV�[0m
2026-03-10T18:12:40.2691044Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

and maybe this??

2026-03-10T18:12:40.2774630Z Branch/tag name 'main' is valid.
2026-03-10T18:12:40.2827294Z ##[group]Run git config user.name "GitHub Actions Bot"
2026-03-10T18:12:40.2827728Z �[36;1mgit config user.name "GitHub Actions Bot"�[0m
2026-03-10T18:12:40.2828079Z �[36;1mgit config user.email "<>"�[0m
2026-03-10T18:12:40.2874157Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}

[shannah]

You should change your workflow to only run on tags. (ie not on push or commit). then create a release Steve Hannah Web Lite Solutions Corp.

…

On Tue, Mar 10, 2026 at 11:49 AM Joe Page ***@***.***> wrote: job-logs2.txt <https://github.com/user-attachments/files/25880084/job-logs2.txt> attaching the GA logs if it helps.. only errors I see are: 2026-03-10T18:12:40.2537480Z VERSION: 1.0.436 2026-03-10T18:12:40.2537714Z ##[endgroup] 2026-03-10T18:12:40.2632870Z ##[group]Run REF_NAME="main" 2026-03-10T18:12:40.2633208Z �[36;1mREF_NAME="main"�[0m 2026-03-10T18:12:40.2633467Z �[36;1m�[0m 2026-03-10T18:12:40.2633900Z �[36;1m# Check if ref name contains only allowed characters (letters, digits, dash, underscore, dot)�[0m 2026-03-10T18:12:40.2634470Z �[36;1mif [[ ! "$REF_NAME" =~ ^[a-zA-Z0-9._-]+$ ]]; then�[0m 2026-03-10T18:12:40.2635186Z �[36;1m echo "Branch/tag name '$REF_NAME' contains illegal characters. Only letters, digits, dash (-), underscore (_), and dot (.) are allowed."�[0m 2026-03-10T18:12:40.2635920Z �[36;1m echo "Skipping action execution due to invalid ref name."�[0m 2026-03-10T18:12:40.2636378Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m 2026-03-10T18:12:40.2636731Z �[36;1m exit 0�[0m 2026-03-10T18:12:40.2636963Z �[36;1mfi�[0m 2026-03-10T18:12:40.2637188Z �[36;1m�[0m 2026-03-10T18:12:40.2637472Z �[36;1m# Check if ref name length exceeds 16 characters�[0m 2026-03-10T18:12:40.2637848Z �[36;1mif [[ ${#REF_NAME} -gt 16 ]]; then�[0m 2026-03-10T18:12:40.2638424Z �[36;1m echo "Branch/tag name '$REF_NAME' is too long (${#REF_NAME} characters). Maximum allowed length is 16 characters."�[0m 2026-03-10T18:12:40.2639088Z �[36;1m echo "Skipping action execution due to ref name length limit."�[0m 2026-03-10T18:12:40.2639561Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m 2026-03-10T18:12:40.2639919Z �[36;1m exit 0�[0m 2026-03-10T18:12:40.2640161Z �[36;1mfi�[0m 2026-03-10T18:12:40.2640380Z �[36;1m�[0m 2026-03-10T18:12:40.2640646Z �[36;1mecho "Branch/tag name '$REF_NAME' is valid."�[0m 2026-03-10T18:12:40.2641053Z �[36;1mecho "JDEPLOY_SKIP_EXECUTION=false" >> $GITHUB_ENV�[0m 2026-03-10T18:12:40.2691044Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} and maybe this?? 2026-03-10T18:12:40.2774630Z Branch/tag name 'main' is valid. 2026-03-10T18:12:40.2827294Z ##[group]Run git config user.name "GitHub Actions Bot" 2026-03-10T18:12:40.2827728Z �[36;1mgit config user.name "GitHub Actions Bot"�[0m 2026-03-10T18:12:40.2828079Z �[36;1mgit config user.email "<>"�[0m 2026-03-10T18:12:40.2874157Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUNWOSSANZ2HMAISJ2VE234QBPTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGMYTCMQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[jpage4500]

I did end up doing that.. it was an extra step but seems like it works (when merging a PR into main I have 1 action create a tag which then kicks off the other action which does the jdeploy) ​ ​The only problem left that I'm having and can't figure out a way around is how to update https://www.jdeploy.com/~hd-dashboard ​It stopped updating this site when I switched from npm to github. Maybe the change is preventing it from being updated -- if so, could someone delete it? ​ ​thanks ​joe ​ ​

…

On Mar 10 2026, at 5:57 PM, Steve Hannah ***@***.***> wrote: You should change your workflow to only run on tags. (ie not on push or commit). then create a release Steve Hannah Web Lite Solutions Corp. On Tue, Mar 10, 2026 at 11:49 AM Joe Page ***@***.***> wrote: > job-logs2.txt > <https://github.com/user-attachments/files/25880084/job-logs2.txt> > > attaching the GA logs if it helps.. only errors I see are: > > 2026-03-10T18:12:40.2537480Z VERSION: 1.0.436 > 2026-03-10T18:12:40.2537714Z ##[endgroup] > 2026-03-10T18:12:40.2632870Z ##[group]Run REF_NAME="main" > 2026-03-10T18:12:40.2633208Z �[36;1mREF_NAME="main"�[0m > 2026-03-10T18:12:40.2633467Z �[36;1m�[0m > 2026-03-10T18:12:40.2633900Z �[36;1m# Check if ref name contains only allowed characters (letters, digits, dash, underscore, dot)�[0m > 2026-03-10T18:12:40.2634470Z �[36;1mif [[ ! "$REF_NAME" =~ ^[a-zA-Z0-9._-]+$ ]]; then�[0m > 2026-03-10T18:12:40.2635186Z �[36;1m echo "Branch/tag name '$REF_NAME' contains illegal characters. Only letters, digits, dash (-), underscore (_), and dot (.) are allowed."�[0m > 2026-03-10T18:12:40.2635920Z �[36;1m echo "Skipping action execution due to invalid ref name."�[0m > 2026-03-10T18:12:40.2636378Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > 2026-03-10T18:12:40.2636731Z �[36;1m exit 0�[0m > 2026-03-10T18:12:40.2636963Z �[36;1mfi�[0m > 2026-03-10T18:12:40.2637188Z �[36;1m�[0m > 2026-03-10T18:12:40.2637472Z �[36;1m# Check if ref name length exceeds 16 characters�[0m > 2026-03-10T18:12:40.2637848Z �[36;1mif [[ ${#REF_NAME} -gt 16 ]]; then�[0m > 2026-03-10T18:12:40.2638424Z �[36;1m echo "Branch/tag name '$REF_NAME' is too long (${#REF_NAME} characters). Maximum allowed length is 16 characters."�[0m > 2026-03-10T18:12:40.2639088Z �[36;1m echo "Skipping action execution due to ref name length limit."�[0m > 2026-03-10T18:12:40.2639561Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > 2026-03-10T18:12:40.2639919Z �[36;1m exit 0�[0m > 2026-03-10T18:12:40.2640161Z �[36;1mfi�[0m > 2026-03-10T18:12:40.2640380Z �[36;1m�[0m > 2026-03-10T18:12:40.2640646Z �[36;1mecho "Branch/tag name '$REF_NAME' is valid."�[0m > 2026-03-10T18:12:40.2641053Z �[36;1mecho "JDEPLOY_SKIP_EXECUTION=false" >> $GITHUB_ENV�[0m > 2026-03-10T18:12:40.2691044Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} > > and maybe this?? > > 2026-03-10T18:12:40.2774630Z Branch/tag name 'main' is valid. > 2026-03-10T18:12:40.2827294Z ##[group]Run git config user.name "GitHub Actions Bot" > 2026-03-10T18:12:40.2827728Z �[36;1mgit config user.name "GitHub Actions Bot"�[0m > 2026-03-10T18:12:40.2828079Z �[36;1mgit config user.email "<>"�[0m > 2026-03-10T18:12:40.2874157Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} > > — > Reply to this email directly, view it on GitHub > <#429 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAUNWOSSANZ2HMAISJ2VE234QBPTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGMYTCMQ> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > — Reply to this email directly, view it on GitHub (#429 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAOOZAL2N3LA4JAZ4LDPZID4QCFTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGQ3DOMA). You are receiving this because you authored the thread.

[shannah]

That's your npm package. Probably best to do it manually with the cli or desktop app. jdeploy publish Steve Hannah Web Lite Solutions Corp.

…

On Tue, Mar 10, 2026 at 4:02 PM Joe Page ***@***.***> wrote: I did end up doing that.. it was an extra step but seems like it works (when merging a PR into main I have 1 action create a tag which then kicks off the other action which does the jdeploy) ​ ​The only problem left that I'm having and can't figure out a way around is how to update https://www.jdeploy.com/~hd-dashboard ​It stopped updating this site when I switched from npm to github. Maybe the change is preventing it from being updated -- if so, could someone delete it? ​ ​thanks ​joe ​ ​ On Mar 10 2026, at 5:57 PM, Steve Hannah ***@***.***> wrote: > > > You should change your workflow to only run on tags. (ie not on push or > > commit). then create a release > > > Steve Hannah > > Web Lite Solutions Corp. > > > > On Tue, Mar 10, 2026 at 11:49 AM Joe Page ***@***.***> wrote: > > > > job-logs2.txt > > > <https://github.com/user-attachments/files/25880084/job-logs2.txt> > > > > > > attaching the GA logs if it helps.. only errors I see are: > > > > > > 2026-03-10T18:12:40.2537480Z VERSION: 1.0.436 > > > 2026-03-10T18:12:40.2537714Z ##[endgroup] > > > 2026-03-10T18:12:40.2632870Z ##[group]Run REF_NAME="main" > > > 2026-03-10T18:12:40.2633208Z �[36;1mREF_NAME="main"�[0m > > > 2026-03-10T18:12:40.2633467Z �[36;1m�[0m > > > 2026-03-10T18:12:40.2633900Z �[36;1m# Check if ref name contains only allowed characters (letters, digits, dash, underscore, dot)�[0m > > > 2026-03-10T18:12:40.2634470Z �[36;1mif [[ ! "$REF_NAME" =~ ^[a-zA-Z0-9._-]+$ ]]; then�[0m > > > 2026-03-10T18:12:40.2635186Z �[36;1m echo "Branch/tag name '$REF_NAME' contains illegal characters. Only letters, digits, dash (-), underscore (_), and dot (.) are allowed."�[0m > > > 2026-03-10T18:12:40.2635920Z �[36;1m echo "Skipping action execution due to invalid ref name."�[0m > > > 2026-03-10T18:12:40.2636378Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > > > 2026-03-10T18:12:40.2636731Z �[36;1m exit 0�[0m > > > 2026-03-10T18:12:40.2636963Z �[36;1mfi�[0m > > > 2026-03-10T18:12:40.2637188Z �[36;1m�[0m > > > 2026-03-10T18:12:40.2637472Z �[36;1m# Check if ref name length exceeds 16 characters�[0m > > > 2026-03-10T18:12:40.2637848Z �[36;1mif [[ ${#REF_NAME} -gt 16 ]]; then�[0m > > > 2026-03-10T18:12:40.2638424Z �[36;1m echo "Branch/tag name '$REF_NAME' is too long (${#REF_NAME} characters). Maximum allowed length is 16 characters."�[0m > > > 2026-03-10T18:12:40.2639088Z �[36;1m echo "Skipping action execution due to ref name length limit."�[0m > > > 2026-03-10T18:12:40.2639561Z �[36;1m echo "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > > > 2026-03-10T18:12:40.2639919Z �[36;1m exit 0�[0m > > > 2026-03-10T18:12:40.2640161Z �[36;1mfi�[0m > > > 2026-03-10T18:12:40.2640380Z �[36;1m�[0m > > > 2026-03-10T18:12:40.2640646Z �[36;1mecho "Branch/tag name '$REF_NAME' is valid."�[0m > > > 2026-03-10T18:12:40.2641053Z �[36;1mecho "JDEPLOY_SKIP_EXECUTION=false" >> $GITHUB_ENV�[0m > > > 2026-03-10T18:12:40.2691044Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} > > > > > > and maybe this?? > > > > > > 2026-03-10T18:12:40.2774630Z Branch/tag name 'main' is valid. > > > 2026-03-10T18:12:40.2827294Z ##[group]Run git config user.name "GitHub Actions Bot" > > > 2026-03-10T18:12:40.2827728Z �[36;1mgit config user.name "GitHub Actions Bot"�[0m > > > 2026-03-10T18:12:40.2828079Z �[36;1mgit config user.email "<>"�[0m > > > 2026-03-10T18:12:40.2874157Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0} > > > > > > — > > > Reply to this email directly, view it on GitHub > > > < #429 (comment)>, > > > or unsubscribe > > > < https://github.com/notifications/unsubscribe-auth/AAUNWOSSANZ2HMAISJ2VE234QBPTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGMYTCMQ> > > > . > > > You are receiving this because you are subscribed to this thread.Message > > > ID: ***@***.***> > > > > > > — > > Reply to this email directly, view it on GitHub ( #429 (comment)), or unsubscribe ( https://github.com/notifications/unsubscribe-auth/AAOOZAL2N3LA4JAZ4LDPZID4QCFTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGQ3DOMA). > > You are receiving this because you authored the thread. > > — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUNWOXGACYSNEFU4WM2ECL4QCNHRAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGUYTIMY> . You are receiving this because you commented.Message ID: ***@***.***>

[jpage4500]

Ok, I think I got it.. the jdeploy page (https://www.jdeploy.com/~hd-dashboard) is only used for apps which are saved on NPM. Must be because I deleted the packages on NPM directly and the link above no longer shows anything. ​ I just have 1 last question regarding deploying but I'll open a new thread for it ​ ​thanks again for your support ​ ​joe​ ​ ​​

…

On Mar 10 2026, at 9:19 PM, Steve Hannah ***@***.***> wrote: That's your npm package. Probably best to do it manually with the cli or desktop app. jdeploy publish Steve Hannah Web Lite Solutions Corp. On Tue, Mar 10, 2026 at 4:02 PM Joe Page ***@***.***> wrote: > > I did end up doing that.. it was an extra step but seems like it works > (when merging a PR into main I have 1 action create a tag which then kicks > off the other action which does the jdeploy) > > ​ > > ​The only problem left that I'm having and can't figure out a way around > is how to update https://www.jdeploy.com/~hd-dashboard > > > ​It stopped updating this site when I switched from npm to github. Maybe > the change is preventing it from being updated -- if so, could someone > delete it? > > ​ > > ​thanks > > ​joe > > ​ > > ​ > > On Mar 10 2026, at 5:57 PM, Steve Hannah ***@***.***> wrote: > > > > > > > You should change your workflow to only run on tags. (ie not on push or > > > > commit). then create a release > > > > > > Steve Hannah > > > > Web Lite Solutions Corp. > > > > > > > > On Tue, Mar 10, 2026 at 11:49 AM Joe Page ***@***.***> wrote: > > > > > > > job-logs2.txt > > > > > <https://github.com/user-attachments/files/25880084/job-logs2.txt> > > > > > > > > > > attaching the GA logs if it helps.. only errors I see are: > > > > > > > > > > 2026-03-10T18:12:40.2537480Z VERSION: 1.0.436 > > > > > 2026-03-10T18:12:40.2537714Z ##[endgroup] > > > > > 2026-03-10T18:12:40.2632870Z ##[group]Run REF_NAME="main" > > > > > 2026-03-10T18:12:40.2633208Z �[36;1mREF_NAME="main"�[0m > > > > > 2026-03-10T18:12:40.2633467Z �[36;1m�[0m > > > > > 2026-03-10T18:12:40.2633900Z �[36;1m# Check if ref name contains only > allowed characters (letters, digits, dash, underscore, dot)�[0m > > > > > 2026-03-10T18:12:40.2634470Z �[36;1mif [[ ! "$REF_NAME" =~ > ^[a-zA-Z0-9._-]+$ ]]; then�[0m > > > > > 2026-03-10T18:12:40.2635186Z �[36;1m echo "Branch/tag name '$REF_NAME' > contains illegal characters. Only letters, digits, dash (-), underscore > (_), and dot (.) are allowed."�[0m > > > > > 2026-03-10T18:12:40.2635920Z �[36;1m echo "Skipping action execution > due to invalid ref name."�[0m > > > > > 2026-03-10T18:12:40.2636378Z �[36;1m echo > "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > > > > > 2026-03-10T18:12:40.2636731Z �[36;1m exit 0�[0m > > > > > 2026-03-10T18:12:40.2636963Z �[36;1mfi�[0m > > > > > 2026-03-10T18:12:40.2637188Z �[36;1m�[0m > > > > > 2026-03-10T18:12:40.2637472Z �[36;1m# Check if ref name length exceeds > 16 characters�[0m > > > > > 2026-03-10T18:12:40.2637848Z �[36;1mif [[ ${#REF_NAME} -gt 16 ]]; > then�[0m > > > > > 2026-03-10T18:12:40.2638424Z �[36;1m echo "Branch/tag name '$REF_NAME' > is too long (${#REF_NAME} characters). Maximum allowed length is 16 > characters."�[0m > > > > > 2026-03-10T18:12:40.2639088Z �[36;1m echo "Skipping action execution > due to ref name length limit."�[0m > > > > > 2026-03-10T18:12:40.2639561Z �[36;1m echo > "JDEPLOY_SKIP_EXECUTION=true" >> $GITHUB_ENV�[0m > > > > > 2026-03-10T18:12:40.2639919Z �[36;1m exit 0�[0m > > > > > 2026-03-10T18:12:40.2640161Z �[36;1mfi�[0m > > > > > 2026-03-10T18:12:40.2640380Z �[36;1m�[0m > > > > > 2026-03-10T18:12:40.2640646Z �[36;1mecho "Branch/tag name '$REF_NAME' > is valid."�[0m > > > > > 2026-03-10T18:12:40.2641053Z �[36;1mecho > "JDEPLOY_SKIP_EXECUTION=false" >> $GITHUB_ENV�[0m > > > > > 2026-03-10T18:12:40.2691044Z shell: /usr/bin/bash --noprofile --norc > -e -o pipefail {0} > > > > > > > > > > and maybe this?? > > > > > > > > > > 2026-03-10T18:12:40.2774630Z Branch/tag name 'main' is valid. > > > > > 2026-03-10T18:12:40.2827294Z ##[group]Run git config user.name > "GitHub Actions Bot" > > > > > 2026-03-10T18:12:40.2827728Z �[36;1mgit config user.name "GitHub > Actions Bot"�[0m > > > > > 2026-03-10T18:12:40.2828079Z �[36;1mgit config user.email "<>"�[0m > > > > > 2026-03-10T18:12:40.2874157Z shell: /usr/bin/bash --noprofile --norc > -e -o pipefail {0} > > > > > > > > > > — > > > > > Reply to this email directly, view it on GitHub > > > > > < > #429 (comment)>, > > > > > > or unsubscribe > > > > > < > https://github.com/notifications/unsubscribe-auth/AAUNWOSSANZ2HMAISJ2VE234QBPTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGMYTCMQ> > > > > > > . > > > > > You are receiving this because you are subscribed to this > thread.Message > > > > > ID: ***@***.***> > > > > > > > > > > > — > > > > Reply to this email directly, view it on GitHub ( > #429 (comment)), > or unsubscribe ( > https://github.com/notifications/unsubscribe-auth/AAOOZAL2N3LA4JAZ4LDPZID4QCFTNAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGQ3DOMA). > > > > > You are receiving this because you authored the thread. > > > > > > — > Reply to this email directly, view it on GitHub > <#429 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAUNWOXGACYSNEFU4WM2ECL4QCNHRAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGUYTIMY> > . > You are receiving this because you commented.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub (#429 (comment)), or unsubscribe (https://github.com/notifications/unsubscribe-auth/AAOOZAIN4EOKX54GA2OPJYT4QC5INAVCNFSM6AAAAACWNM5XDOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMBXGYYDIOI). You are receiving this because you authored the thread.