dotnet-foundation / dotnet-foundation/projects
[Project Support]: Reaqtor code signing needs update
@ChrisSfanos is already working on this.
Since Jul 9, 2026.
- Dominant language
- No language data
- Stars
- 157
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Project
Reaqtor
Project Url
https://github.com/reaqtive/reaqtor/
Description
The Reaqtor project (related to, but not to be confused with the Rx.NET, the Reactive Extensions for .NET) has been dormant for a while, but we've been doing more work on it recently. This has revealed that the code signing no longer works.
With Rx.NET, we had to move onto a newer mechanism for code signing (back in 2024 I think). I'm pretty sure Reaqtor was set up on the old mechanism (back in 2021). Now that we're getting errors trying to code sign, I presume it means we need to move it onto the current way of doing things.
You can see a package signing failure here: https://dev.azure.com/dotnet/Reaqtor/_build/results?buildId=128824&view=logs&j=fc3e957c-3198-5bbe-afe5-3dcea2dcf94c&t=526581ce-a63b-504b-75df-a54aa78507af
Due By
2026/07/20
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.