Looks like others had the same idea like me and got it working with a PAT: https://github.com/release-drafter/release-drafter/issues/1081#issuecomment-1050099868 Or locally like it does work for you.
[email protected] schrieb am Freitag, 25. Februar 2022 um 09:36:38 UTC+1: > Weirdly if I run all the steps locally from the GitHub action I'm getting > the right results =/ > > > https://github.com/jenkinsci/jenkins-infra-test-plugin/runs/5330785488?check_suite_focus=true > > On Thu, 24 Feb 2022 at 23:37, Alex <[email protected]> wrote: > >> I got it working by exchanging the GitHub token in the workflow with a >> PAT: >> https://github.com/jenkinsci/purge-build-queue-plugin/commit/3e0e709bf62ec15a84d5bf4e2e81a98ace7b79bf >> >> I guess, GitHub either changed or broke something (both I'm currently >> unaware of), because the regular GH token suffices and grants read/write >> perms to all scopes, unless you change the workflow permission to read only >> for content, but that doesn't apply here. >> Alex schrieb am Donnerstag, 24. Februar 2022 um 23:57:39 UTC+1: >> >>> To amend my comment on the dark-theme-plugin PR, I got the action >>> somewhat of working by wiping the additional drafts and keeping one that >>> covers all. >>> I'm using release-drafter via GitHub actions outside of Jenkins too and >>> have repositories with several drafts with different entries, so I'm not >>> sure whether that is an actual issue with CD or GH actions/release-drafter >>> itself. >>> However, I didn't make it as far as Tim, because the "release" step >>> fails with a 403 on deployment for me. That failure creates a new draft and >>> we're basically back at step one. >>> >>> >>> [email protected] schrieb am Donnerstag, 24. Februar 2022 um 23:18:30 >>> UTC+1: >>> >>>> We were just discussing this here: >>>> >>>> https://github.com/jenkinsci/dark-theme-plugin/pull/170#issuecomment-1050263227 >>>> >>>> By using a manual trigger to bypass the interesting category check and >>>> publishing the release notes myself I was able to get the release out >>>> >>>> On Thu, 24 Feb 2022 at 22:06, José Lamas Ríos <[email protected]> wrote: >>>> >>>>> Maybe unrelated but I've just noticed that the release draft >>>>> <https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d> >>>>> >>>>> that was just created and is listed as the most recent one but shows a >>>>> Dec >>>>> 10 2021 date... >>>>> >>>>> There is in fact another release >>>>> <https://github.com/jenkinsci/genexus-plugin/releases/tag/next> on >>>>> that date that is not in draft state but (probably due to some error on >>>>> my >>>>> part) got published while keeping the 'next' tag / name. >>>>> >>>>> I'll later try renaming or deleting the old release and check if that >>>>> fixes the problem. >>>>> >>>>> >>>>> >>>>> >>>>> On Thursday, February 24, 2022 at 6:52:46 PM UTC-3 José Lamas Ríos >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I'm having problems with the automated release workflow for >>>>>> genexus-plugin <https://github.com/jenkinsci/genexus-plugin>. >>>>>> >>>>>> For instance, this CD run at >>>>>> https://github.com/jenkinsci/genexus-plugin/runs/5325279945 >>>>>> >>>>>> After the successful build it gets to create the release draft, but >>>>>> then seems to fail at finding it with an interesting category, so the >>>>>> release is not fired. >>>>>> >>>>>> The draft release was created at >>>>>> https://github.com/jenkinsci/genexus-plugin/releases/tag/untagged-1934fa52b049ad8ace3d >>>>>> >>>>>> and running these commands on my terminal does seem to work: >>>>>> >>>>>> McJLR:~jlr$ RESULT=$(gh api /repos/jenkinsci/genexus-plugin/releases >>>>>> | jq -e -r '.[] | select(.draft == true and .name == "next") | .body' | >>>>>> egrep "$INTERESTING_CATEGORIES" || echo 'failed') >>>>>> >>>>>> McJLR:~ jlr$ echo $RESULT >>>>>> >>>>>> ## 🐛 Bug fixes >>>>>> >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Thanks in advance, >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/c742b7c1-e2e2-456a-a6ab-d2a56f76fb36n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/badbb90d-1358-48c4-809a-0462c08c9c00n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/badbb90d-1358-48c4-809a-0462c08c9c00n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/de8037a9-c7fe-4142-885d-7ccb8b52eb1bn%40googlegroups.com.
