-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add patch version to repo tags (v1.1.0 instead of v1.1) #43
Comments
+1 for this.
|
You can also add this to exclude github.com/SermoDigital/jose v0.9.1 That will force |
+1 for this. |
@ericlagergren Would you mind running this command for us please: git clone git@github.com:SermoDigital/jose.git
cd jose/
git checkout v1.1
git tag v1.1.0
git push --tags It would help a ton. Please and thank you! |
So is this package still active or should someone create a fork? Because without modules support using this package is going to be awkward. |
@kerak19 Here's an open source social experiment that may be worth trying:
I think someone just has to have enough "skin in the game" to make it happen, but it looks like there aren't any people aside from the author with more than 2 commits, so it's a tough sell. Being a maintainer is a thankless job... :-/ |
Hi guys. It's been a while since I've worked here. I reached out and got confirmation that a fork is the best way to move forward right now. |
Do any of you have a vested interested in maintaining a fork of this project and vetting others to add who want to help? All those who have contributed or forked@ericlagergren, @mark-adams, @zgiber, @ifraixedes, @magiconair, @tw1nk, @yageek, @eliquious, @TheHippo, @supershabam, @kmulvey, @andrefreitas, @tooooolong, @30mw002, @akutz, @Andresferreira3191, @bmpickford, @briankassouf, @BryanSingh, @cognusion, @cpl-qlik, @DavadDi, @Gluoo, @robbyoconnor, @sharonjl, @golint-fixer, @husnifirmansyah, @insionng, @jayantnd, @josuehennemann, @jvthanh, @kavonm, @lanziliang, @ll837448792, @melotusme, @MentalPower, @MEX7, @mohammed90, @mudzot, @naufalfmm, @niksmith, @onef9day, @oren, @owenliu1122, @PattaraponLertratananont, @peterwillcn, @presto78, @rjansen, @sevaorlov, @showz, @smartrevolution, @bhanditz, @spivegin, @sthapaun, @stonewl897, @svarlamov, @tirithen, @tomwganem, @vadimline, @winonone, @zensh How I got that listI grabbed everyone's names with this by visiting https://github.com/SermoDigital/jose/graphs/contributors and running this: var usernames = {};
$$('[data-hovercard-type="user"]').forEach(function (el) {
usernames[el.href.replace("https://github.com/", "@").toLowerCase()] = true;
});
console.log(Object.keys(usernames).join(", ")); and then going to https://github.com/SermoDigital/jose/network/members and running this: var usernames = {};
var lastList = "" // but with the last list instead of an empty string
lastList.split(/,\s+/).forEach(function (name) {
usernames[name.toLowerCase()] = true;
});
$$('[data-octo-dimensions="link_type:self"]').forEach(function (el) {
usernames[el.href.replace("https://github.com/", "@").toLowerCase()] = true;
});
console.log(Object.keys(usernames).join(", ")); |
@ericlagergren Is there a way that you can have the README updated to point to a "blessed" fork or transfer ownership of the repo, assuming someone speaks up? If within 72 hours no one else responds, I'd be happy to create a fork and bless myself, but it would be primarily just to establish a simple contributor policy, vet potential contributors, and enable them to get patches in and potentially share responsibility (I don't want to be a sole maintainer). |
We've mostly moved away from this package because it creates RFC-incompatible JWTs that can only be verified by itself. |
I'm not up to maintaining a fork myself... -- go ahead @coolaj86 |
@coolaj86 i don't know if i'am competent enough - i haven't read the RFCs yet. Tbh for starters i think Go modules support would be sufficient |
Unfortunately, I cannot participate on it for now; I used this package more than 2.5 years ago, I'm not competent enough in such RFCs and right now I don't have that much free time. |
+1 |
Shall we close this issue? |
Was it done? If not, then no. |
Using
|
The
go mod
tool does not recognize SemVersion without the patch version. Therfor it falls back to the v0.9.1 version as its the only tag with patch number in your repo. Could you please tag the repo for v1.1.0 and v1.0.0?The text was updated successfully, but these errors were encountered: