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

SemVer compatible release #170

Open
VasekPurchart opened this issue Dec 1, 2017 · 3 comments
Open

SemVer compatible release #170

VasekPurchart opened this issue Dec 1, 2017 · 3 comments
Assignees

Comments

@VasekPurchart
Copy link

VasekPurchart commented Dec 1, 2017

Hello, could you please tag the latest r2017-06 release as a SemVer compatible version? So maybe something like 0.3.0 based on the previous releases I see.

Otherwise for example Composer for PHP (and maybe some of the other package managers as well) can not pick up these releases and have to rely on fetching master or something like that, which is a bad practice.

@antonioribeiro
Copy link

@VasekPurchart You can require that specific tag on Composer this way:

"snowplow/referer-parser": "dev-master#r2017-06",

But it's locked to that particular tag and we would not get updates when a new version (2017-12) is tagged. So using SemVer version numbering system would be really nice.

@VasekPurchart
Copy link
Author

Yea, I know that's what we are at right now, but that also means for example that it's not cached by Composer etc.

@ndberg
Copy link

ndberg commented Nov 25, 2020

@antonioribeiro,

if I use:
"snowplow/referer-parser": "dev-master#r2017-06",

I don't get any php files at all, just some other stuff.

Am I missing something?

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

4 participants