Skip to content
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

Open
andrejvanderzee opened this issue Aug 31, 2018 · 19 comments
Open

Add patch version to repo tags (v1.1.0 instead of v1.1) #43

andrejvanderzee opened this issue Aug 31, 2018 · 19 comments

Comments

@andrejvanderzee
Copy link

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?

@frasercobb
Copy link

+1 for this.
As a workaround I have forked this repo and added the tag myself, then replaced this package in my go.mod like so:

replace github.com/SermoDigital/jose => <PATH_TO_FORKED_REPO>/jose

@andrejvanderzee
Copy link
Author

andrejvanderzee commented Sep 19, 2018

You can also add this to go.mod:

exclude github.com/SermoDigital/jose v0.9.1

That will force master as there are no other correct SemVer tags on the repo.

@NickCiao
Copy link

+1 for this.

@coolaj86
Copy link

@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!

@kerak19
Copy link

kerak19 commented Feb 14, 2019

So is this package still active or should someone create a fork? Because without modules support using this package is going to be awkward.

@coolaj86
Copy link

coolaj86 commented Feb 14, 2019

@kerak19 Here's an open source social experiment that may be worth trying:

  1. Create a fork
  2. Open an issue titled "Official maintenance fork: <>" with a description of your goals for the project
  3. Message the other forkers to inform them of your fork (and maybe try to merge some things)
  4. See if you can actually get people to agree to continue development / maintenance.

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... :-/

@ericlagergren
Copy link
Contributor

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.

@coolaj86
Copy link

coolaj86 commented Feb 14, 2019

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 list

I 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(", "));

@coolaj86
Copy link

@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).

@jefferai
Copy link

We've mostly moved away from this package because it creates RFC-incompatible JWTs that can only be verified by itself.

@robbyoconnor
Copy link

I'm not up to maintaining a fork myself... -- go ahead @coolaj86

@kerak19
Copy link

kerak19 commented Feb 15, 2019

@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

@ifraixedes
Copy link
Contributor

ifraixedes commented Feb 15, 2019

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.
Thanks for the ping.

@josuehennemann
Copy link

josuehennemann commented Feb 15, 2019 via email

@brianvoe
Copy link

@macinnir
Copy link

+1 for this.
As a workaround I have forked this repo and added the tag myself, then replaced this package in my go.mod like so:

replace github.com/SermoDigital/jose => <PATH_TO_FORKED_REPO>/jose

+1
This is a pretty simple change of adding a proper semver tag. In the meantime, I also have a fork:
https://github.com/macinnir/jose

@andrefreitas
Copy link
Contributor

Shall we close this issue?

@robbyoconnor
Copy link

Was it done? If not, then no.

@sgmheyhey
Copy link

Using go mod, how to avoid to get v0.9.1 but get v1.1
(not as v1.1.0 but as v0.9.2)

  1. make go.mod file
go mod init jwt
go mod tidy
  1. get a pseudo-version for not tagged version
go get github.com/SermoDigital/jose@master
go get: upgraded github.com/SermoDigital/jose v0.9.1 => v0.9.2-0.20180104203859-803625baeddc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests