Cut v0.6.0 release#62
Conversation
|
👋 I see @tnull was un-assigned. |
tankyleo
force-pushed
the
2026-05-cut-0.6.0
branch
from
c720e89 to
ecf1618
Compare
|
|
||
| > [!WARNING] | ||
| > This release of `vss-client-ng` requires a corresponding upgrade to `vss-server`. `vss-server` | ||
| > should be upgraded first to at least commit `f728209e2f7ad4dc146b1f90d6081e1226705a8f`, then |
There was a problem hiding this comment.
Hmm, shouldn't we rather just cut a vss-server 0.1 soon/now and then have the client depend on it rather than on some arbitrary revision?
There was a problem hiding this comment.
Remove the java version then cut a release ? I was hoping to merge a usage-limits fix before doing the first release of vss-server.
There was a problem hiding this comment.
Upon further thought you are right, I think we can drop the java implementation, and tag v0.1.0-alpha.1 on vss-server what do you think ?
There was a problem hiding this comment.
Upon further thought you are right, I think we can drop the java implementation, and tag
v0.1.0-alpha.1on vss-server what do you think ?
Sounds good to me. IMO the limits could also be a patch release (assuming API doesn't break), but up to you.
I added a commit to lightningdevkit/vss-server#100 that pulls the main branch here and runs the backwards compat test against it. |
3 participants
No description provided.