chore(release): prepare for publishing

[devolutionsbot]

🤖 New release

• sspi: 0.15.14 -> 0.15.15 (✓ API compatible changes)

Changelog

sspi

[0.15.15] - 2025-07-07

Features

• Server-side Kebreros implementation (feat(sspi): server-side Kebreros implementation #440) (943a297edd)

Bug Fixes

• Server-side Kerberos fixes (feat(sspi): server-side Kerberos fixes #457) (27ce28dad5)

• Kerberos server MIC token generation and validation (fix(sspi): Kerberos server MIC token generation and validation #464) (12fbd706a8)

• Kerberos server WRAP token generation and validation (fix(sspi): Kerberos server WRAP token generation and validation #463) (4bbe4071c8)

---

This PR was generated with release-plz.

[TheBestTvarynka]

@CBenoit I think the new version should be 0.16. In the least PR, I made the accept_security_context function async (now it returns a generator). This is a breaking change. What do you think?

[CBenoit]

I think the new version should be 0.16. In the least PR, I made the accept_security_context function async (now it returns a generator). This is a breaking change. What do you think?

Makes sense, but are you referring to this function?

sspi-rs/src/kerberos/server/mod.rs

Line 105 in 4bbe407

pub async fn accept_security_context(

It seems that it was added, and not modified, unless I’m missing something 🤔

But anyway, it’s still a bit risky to not perform a major bump given the big number of changes, so I rather agree with a 0.16 bump.

By the way, it’s possible to specify that a commit is bringing a breaking change following the conventional commit spec: https://www.conventionalcommits.org/en/v1.0.0/
It would be best to properly document that using a ! after the type/scope, or adding the BREAKING CHANGE: footer along a description of the breakage.

[TheBestTvarynka]

By the way, it’s possible to specify that a commit is bringing a breaking change following the conventional commit spec: conventionalcommits.org/en/v1.0.0

Got it! 👍

[TheBestTvarynka]

Makes sense, but are you referring to this function?

I am talking about this change: https://github.com/Devolutions/sspi-rs/pull/440/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759L1270-R1283

[CBenoit]

Makes sense, but are you referring to this function?

I am talking about this change: https://github.com/Devolutions/sspi-rs/pull/440/files#diff-b1a35a68f14e696205874893c07fd24fdb88882b47c23cc0e0c80a30c7d53759L1270-R1283

Indeed! This to be a breaking change to me, but the tool (cargo-semver-checks) didn’t catch it! Thank you for pointing it