Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 6 commits
- 8 files changed
- 5 contributors
Commits on May 31, 2026
Commits on Jun 2, 2026
-
fix: signing improvements (#160)
When the default keystore alias/password fails, we log that failure and retry with legacy credentials. Before, the primary failure was swallowed and if the legacy stuff also failed, only the legacy error surfaced. Now we log both the primary failure and legacy error if legacy also fails (legacy attached as suppressed).
-
chore: Release v1.9.1-dev.3 [skip ci]
## [1.9.1-dev.3](v1.9.1-dev.2...v1.9.1-dev.3) (2026-06-02) ### Bug Fixes * signing improvements ([#160](#160)) ([166f940](166f940))
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.9.1-dev.2...v1.9.1-dev.3