starred/sshsrv
1
0
Fork 0
mirror of https://github.com/Crosse/sshsrv.git synced 2026-04-25 03:45:55 +03:00
Code Issues 2 Projects Releases 2 Packages Wiki Activity

[GH-ISSUE #7] Semantic Version number #5

New issue
Closed
opened 2026-02-26 17:45:08 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 17:45:08 +03:00
Owner
Copy link

Originally created by @joshbode on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/Crosse/sshsrv/issues/7

I use a tool called Mise to manage the installation of tools into my development environment and one of the tools I install is sshsrv.

To identify the available versions of go-based tools, Mise executes the following command internally:

$ go list -m -versions -json github.com/Crosse/sshsrv
{
        "Path": "github.com/Crosse/sshsrv"
}

Usually there would be a Versions key in the response, however for sshsrv there isn't any (see https://github.com/jdx/mise/issues/3597).

I believe that go list requires full semantic versions (e.g. vX.Y.Z) to include a specific version in the go list -m -versions response, however the only version tagged in the sshsrv repo is v1.0 (rather than v1.0.0).

Would it be possible to include a tag for v1.0.0, please?

Originally created by @joshbode on GitHub (Dec 20, 2024). Original GitHub issue: https://github.com/Crosse/sshsrv/issues/7 I use a tool called Mise to manage the installation of tools into my development environment and one of the tools I install is `sshsrv`. To identify the available versions of `go`-based tools, Mise executes the following command internally: ``` $ go list -m -versions -json github.com/Crosse/sshsrv { "Path": "github.com/Crosse/sshsrv" } ``` Usually there would be a `Versions` key in the response, however for `sshsrv` there isn't any (see https://github.com/jdx/mise/issues/3597). I believe that `go list` requires full semantic versions (e.g. `vX.Y.Z`) to include a specific version in the `go list -m -versions` response, however the only version tagged in the `sshsrv` repo is `v1.0` (rather than `v1.0.0`). Would it be possible to include a tag for `v1.0.0`, please?
kerem closed this issue 2026-02-26 17:45:09 +03:00
kerem commented 2026-02-26 17:45:09 +03:00
Author
Owner
Copy link

@Crosse commented on GitHub (Dec 21, 2024):

I've pushed a new tag:

$ go list -m -versions -json github.com/Crosse/sshsrv
{
        "Path": "github.com/Crosse/sshsrv",
        "Versions": [
                "v1.0.1"
        ],
        "Main": true,
        "Dir": "/Users/seth/code/mine/sshsrv",
        "GoMod": "/Users/seth/code/mine/sshsrv/go.mod",
        "GoVersion": "1.23.0"
}

(No code change; I probably should have tagged it as v1.0.0, but oh well.) Hopefully this will fix your immediate issue? Let me know if it doesn't.

I honestly didn't realize people used this all that much. I've got some updates I need to make, so maybe there will be a v1.1.0 soon…

<!-- gh-comment-id:2557990766 --> @Crosse commented on GitHub (Dec 21, 2024): I've pushed a new tag: ``` $ go list -m -versions -json github.com/Crosse/sshsrv { "Path": "github.com/Crosse/sshsrv", "Versions": [ "v1.0.1" ], "Main": true, "Dir": "/Users/seth/code/mine/sshsrv", "GoMod": "/Users/seth/code/mine/sshsrv/go.mod", "GoVersion": "1.23.0" } ``` (No code change; I probably should have tagged it as v1.0.0, but oh well.) Hopefully this will fix your immediate issue? Let me know if it doesn't. I honestly didn't realize people used this all that much. I've got some updates I need to make, so maybe there will be a v1.1.0 soon…
kerem commented 2026-02-26 17:45:09 +03:00
Author
Owner
Copy link

@joshbode commented on GitHub (Dec 21, 2024):

Awesome! Thank you.

I've been using sshsrv in conjunction with pktriot (as an alternative to ngrok), since it provides a stable (but initially randomly allocated) port number for tunnels (unlike ngrok which is random each time unless you pay). I got sick of remembering which port was allocated where, but using the SRV record is an elegant way to expose the allocated port :)

<!-- gh-comment-id:2558077244 --> @joshbode commented on GitHub (Dec 21, 2024): Awesome! Thank you. I've been using sshsrv in conjunction with pktriot (as an alternative to ngrok), since it provides a stable (but initially randomly allocated) port number for tunnels (unlike ngrok which is random each time unless you pay). I got sick of remembering which port was allocated where, but using the SRV record is an elegant way to expose the allocated port :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.0.2
v1.0.1
v1.0
Labels
Clear labels   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sshsrv#5
No description provided.