Skip to content
This repository has been archived by the owner on Mar 11, 2022. It is now read-only.

Broken path #21

Merged
merged 1 commit into from
Oct 13, 2015
Merged

Broken path #21

merged 1 commit into from
Oct 13, 2015

Conversation

olssonm
Copy link
Contributor

@olssonm olssonm commented Oct 13, 2015

Somehow a flaw slipped through in the last update – causing entire projects to break on composer update... Haven't had the chance/time to spot anything else that might be wrong.

Error occurs on composer update, if you haven't specified a specific release (i.e. 1.0.0) but instead for example ~1.0 which would bring in 1.1.0.

Somehow a major flaw slipped through in the last update…?
@douglasmiguel
Copy link

I had the same problem, please approve the correction.

@olssonm
Copy link
Contributor Author

olssonm commented Oct 13, 2015

@douglasmiguel In the meanwhile, you can include this in your composer:

"repositories": [
        {
            "type": "git",
            "url": "https://github.com/olssonm/laravel-gravatar.git"
        }
]

And set "thomaswelton/laravel-gravatar" to"master". Then you will get the code in my repository instead.

Or, of course use and older version =)

@douglasmiguel
Copy link

@olssonm Thank you.

I fix the path manually at the vendor.
It will not get me in trouble until it comes out the correction.

Best regards,

AntoineAugusti added a commit that referenced this pull request Oct 13, 2015
@AntoineAugusti AntoineAugusti merged commit e01b473 into thomaswelton:master Oct 13, 2015
@AntoineAugusti
Copy link
Collaborator

@olssonm @douglasmiguel Going to release a new version right now, sorry about it.

@AntoineAugusti
Copy link
Collaborator

@olssonm @douglasmiguel Just retagued v1.1 https://github.com/thomaswelton/laravel-gravatar/releases/tag/1.1.0. Let me know if composer update gives you any trouble

@douglasmiguel
Copy link

Everything is OK!
Thank you.

@olssonm
Copy link
Contributor Author

olssonm commented Oct 13, 2015

@AntoineAugusti Great! Seems to work now correctly again. Thanks for the swift work =)

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants