Jussi Kukkonen

Updating status: * This has mostly been waiting for my comments, I've now added some to the PR * I'm currently leaning towards accepting the fix for the immediate issue...

### Status update * further testing in the PR seems to show that my initial expectation was correct: protecting access just to the symlink only moves the problem elsewhere. We...

making some notes: * some sources claim msvcrt.locking() requires (wihtout documenting it) a non-zero file but every test I do seems to not require it (the byte range can be...

So based on the screenshot: * other builds work but python 3.10 fails: dependency resolution can depend on python version so that would make some sense... * except we now...

> Can you provide complete logs? specifically I'd like to see the complete log of the the workflow step that runs sigstore/gh-action-sigstore-python -- at least from a failing run. Maybe...

Actually, there are two problems: 1. the python version management has not been released yet -- I believe just a new release will likely fix your current issue 2. However,...

I would suggest: * let's fix #258 * make a new release asap My apologies for not releasing the python version management stuff earlier: I really thought that was in...

@ModeSevenIndustrialSolutions if you are able to test your workflow with `sigstore/gh-action-sigstore-python@main` that would be helpful. I will try to do a release anyway tomorrow but would be good to see...

I believe this issue is resolved with 3.2.0 release

I think specific action items were not found on this attempt so I'm closing for now: The contribution docs are linked from the README already, adding the same links again...