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
2 days ago 4.3.4 was released on the npm registry and broke our build (issue here: #49 )
Took a while to discover since we didn't even realize that graphy had a new release.
Would be nice if the release could be added to the changelog.
Additionally, I personally appreciate projects using git tags and by extension github releases to document new releases, so if you're not against using them (you seem to have been using tags up until 4.3.0) it would be nice if they could be added.
The text was updated successfully, but these errors were encountered:
My apologies! I am not sure what caused this either but I will look into it today and make sure to get a patch out. I also usually rely on npm to automatically create tags that github recognizes as releases but my workflow changed recently so it's possible I need to fix something on my end. Thanks for the report.
2 days ago 4.3.4 was released on the npm registry and broke our build (issue here: #49 )
Took a while to discover since we didn't even realize that graphy had a new release.
Would be nice if the release could be added to the changelog.
Additionally, I personally appreciate projects using git tags and by extension github releases to document new releases, so if you're not against using them (you seem to have been using tags up until 4.3.0) it would be nice if they could be added.
The text was updated successfully, but these errors were encountered: