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
ERROR: Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} #1125
Comments
delete the draft. |
hi @jetersen deleted the draft but it was still no use hence reopened the issue |
@sumanth-sure whats the on conditions for your github action? |
on condition
|
I am not sure what your trying to achieve with that workflow? releaseDrafter is not able to generate tags from a pull requests. You want to do that on push to a branch. |
Apologies for the confusion we use the tag received from the release drafter to bump up the version in PR and commit with version new Version.
In This process we are getting the above error |
@jetersen any help on this if possible |
as I said, release drafter is not able to generate drafts from a pull requests. You could try and point the commitish to
|
처음 릴리즈에 대한 문제였는지를 확인하고자, PR할 때마다로 바꾸어 테스트한다. 다음 링크를 보니 push로만 가능하다고 한다. 따라서 push에서 계속 테스트해보고, 마지막에 스쿼시해야겠다...! release-drafter/release-drafter#1125 답변 중: I am not sure what your trying to achieve with that workflow? releaseDrafter is not able to generate tags from a pull requests. You want to do that on push to a branch.
처음 릴리즈에 대한 문제였는지를 확인하고자, PR할 때마다로 바꾸어 테스트한다. 다음 링크를 보니 push로만 가능하다고 한다. 따라서 push에서 계속 테스트해보고, 마지막에 스쿼시해야겠다...! release-drafter/release-drafter#1125 답변 중: I am not sure what your trying to achieve with that workflow? releaseDrafter is not able to generate tags from a pull requests. You want to do that on push to a branch.
뭔가 버저닝이 초기에 잘 되지 않는 현상이 있는 듯하다. 처음 릴리즈에 대한 문제였는지를 확인하고자, PR할 때마다로 바꾸어 테스트한다. 다음 링크를 보니 push로만 가능하다고 한다. 따라서 push에서 계속 테스트해보고, 마지막에 스쿼시해야겠다...! release-drafter/release-drafter#1125 답변 중: I am not sure what your trying to achieve with that workflow? releaseDrafter is not able to generate tags from a pull requests. You want to do that on push to a branch. :construction_worker: label name 변경 아무래도 label name에서 문제인지 테스트를 한다. :test_tube: Release draft default로 변경되는 것인지 테스트
I met this issue today, any fix yet? |
Just started seeing this same error after enabling the autolabeler. Is there a way to limit the action to only updating the draft release on PR merge while still running the autolabeler on the PR?
Guessing that the separate triggers for updating the draft release vs autolabeler is coming in v6 #1204 |
@phatblat Have you resolved this issue yet? I tried many configs but still can't make my workflow work 😢 |
Same here! Auto labeling is working but I started seeing this error. |
anyone with a workaround in the last month? |
I had the same issue and have an easy fix. Maybe it can work for you. New Github repositories do not have "master" as first branch but "main". The error could be catched and explained ^^ |
To reiterate the above, it's failing on the
To avoid this error, either:
|
Maybe the docs could suggest always using |
@tekumara for some reason this doesn't trigger workflow run as with
Using |
Error: ``` Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} ``` Fixes: release-drafter/release-drafter#1125
* ref(workflows): consolidate workflows based on their purpose This also renames the workflows to make their naming more consistent and adding a naming convention Fixes: #6166 Fixes: #6167 * fix(workflows): use correct name for patch * fix(workflow): docker unit tests * fix(release): validation error Error: ``` Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} ``` Fixes: release-drafter/release-drafter#1125 * fix(workflows): reference correct name * fix: remove extra workflow * fix(workflows): use larger runners * fix(workflow): remove code already in docker unit-test * fix(unit-tests): start zebra the right way * fix: typo in patch name * chore: move job to logical order * imp(workflows): use better name for gcp tests * add: missing merge changes * chore: use better name for find-disks * fix(ci): use the `entrypoint.sh` to change the Network * fix(ci): add missing `ZEBRA_CONF_PATH` variable * fix(ci): allow to build the entrypoint file with testnet * fix(entrypoint): allow to create a dir and file with a single variable * refactor: test config file in CI and CD with a reusable workflow * fix(ci): wrong name used * fix(ci): use checkout * fix(ci): improve docker config tests * fix(ci): use better name for protection rules * Fix changed workflow file name in docs patch file * Apply suggestions from code review Co-authored-by: teor <teor@riseup.net> Co-authored-by: Arya <aryasolhi@gmail.com> * fix(cd): depend on file tests * fix(docs): adapt to new workflow name * fix: revert test coverage on CD * chore: reduce diff * fix(ci): allow using variable images for reusable workflows * fix(dockerfile): use variables or default for config path and file * fix(entrypoint): if `$ZEBRA_CONF_PATH` is set, do not override it * Fix patch job names and remove failure job testnet dependencies --------- Co-authored-by: teor <teor@riseup.net> Co-authored-by: Arya <aryasolhi@gmail.com>
* ref(workflows): consolidate workflows based on their purpose This also renames the workflows to make their naming more consistent and adding a naming convention Fixes: #6166 Fixes: #6167 * fix(workflows): use correct name for patch * fix(workflow): docker unit tests * fix(release): validation error Error: ``` Validation Failed: {"resource":"Release","code":"invalid","field":"target_commitish"} ``` Fixes: release-drafter/release-drafter#1125 * fix(workflows): reference correct name * fix: remove extra workflow * fix(workflows): use larger runners * fix(workflow): remove code already in docker unit-test * fix(unit-tests): start zebra the right way * fix: typo in patch name * chore: move job to logical order * imp(workflows): use better name for gcp tests * ref(workflow): use a single job to run GCP tests * fix(ci): do not format existing cached states if required * test: wait for the instance to be fully ready * fix(ci): use correct logic before formating * fix: use correct condition * fix: get more information * fix(ci): use better shell handling and upgrade OS * fix(ci): use better approach * fix: `$DISK_OPTION` is not being correctly passed * fix typo * fix: more typos * fix: use busybox * fix: mount Docker volume at run and not before * fix: use correct condition and simpler while * add: missing merge changes * chore: use better name for find-disks * fix(ci): use the `entrypoint.sh` to change the Network * fix(ci): add missing `ZEBRA_CONF_PATH` variable * fix(ci): considerate new updates to jobs * fix(ci): allow to build the entrypoint file with testnet * fix(entrypoint): allow to create a dir and file with a single variable * fix(ci): add missing jobs to `failure-issue` * Apply suggestions from code review Co-authored-by: teor <teor@riseup.net> * fix(ci): use better comment * refactor: test config file in CI and CD with a reusable workflow * fix(ci): wrong name used * fix(ci): use checkout * fix(ci): improve docker config tests * fix(ci): use better name for protection rules * chore: missing merge conflicts --------- Co-authored-by: teor <teor@riseup.net>
If I change it to |
Use `commitish: main` as in release-drafter/release-drafter#1125 (comment)
Use `commitish: main` as in release-drafter/release-drafter#1125 (comment)
Hi support,
I am not able to get the release tag value from release drafter. I have the following error message in github action
Workflow file
The text was updated successfully, but these errors were encountered: