You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey @youngj, would you mind tagging a v1.0.1 release at this hash? 41dd2b7
That was, packagist.org will create the metadata for a new release, allowing depending projects like drush to clean up their composer.json files.
I'm sure others would appreciate another tag at the head of master as well, but I'm unfamiliar with those changes and not sure what version to bump.
If you wouldn't mind doing this (or tranfering the repo to another maintainer) it would really help keep those who depend on it from fragmenting the network graph any more than it needs to be :)
The text was updated successfully, but these errors were encountered:
Hey @youngj, would you mind tagging a
v1.0.1
release at this hash?41dd2b7
That was, packagist.org will create the metadata for a new release, allowing depending projects like drush to clean up their composer.json files.
I'm sure others would appreciate another tag at the head of master as well, but I'm unfamiliar with those changes and not sure what version to bump.
If you wouldn't mind doing this (or tranfering the repo to another maintainer) it would really help keep those who depend on it from fragmenting the network graph any more than it needs to be :)
The text was updated successfully, but these errors were encountered: