Radek Antoniuk

@olamy does adding PCT tests for this plugin still make sense?

I don't see `PCT` in https://github.com/jenkinsci/jenkins/blob/master/Jenkinsfile so I guess this is no longer neeeded or needs refactoring.

I just looked at the API and it seems that there is a difference between [Jira Software projects and Jira ServiceDesk projects](https://community.developer.atlassian.com/t/post-an-internal-comment-using-v3-api/59983). Which usecase did you have in mind here?

``` $ cat .semantic-release.toml [semantic_release] assets = [] commit_message = "{version}\n\nauto-version by python-semantic-release" commit_parser = "angular" logging_use_named_masks = false major_on_zero = true tag_format = "v{version}" [semantic_release.branches.issue] match = ".*" prerelease_token...

My action configuration is too complex to show, but I would guess this might somehow be related to either: - not providing the token (this is anyway noop so should...

@wardi do you have any immediate suggestion to add anything in the downstream Dockerfile that would make it work?

I actually went the other way round and just added: ``` RUN pip3 install -r https://raw.githubusercontent.com/ckan/ckan/refs/heads/2.11/dev-requirements.txt ``` to my Dockerfile along other plugins. Just as stated in the linked ckan/ckan...

@corymhall I see some `invalid credentials` error on the auto-merge check, I guess that's not my fault ;-)

@corymhall should this failing check fire up from contributions from forks? Should I do any updates on my side ?

Thanks! @corymhall do you have any timeline for v2 release? If there are any 'stoppers', could you maybe mark them via a _milestone_ or a label so I could watch/help...