-
Notifications
You must be signed in to change notification settings - Fork 8
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
Publish Latest Changes #5
Comments
Sure I'll look into this tonight
…On Fri, Jan 24, 2020, 10:15 AM Kyrsten Kelly ***@***.***> wrote:
My coworker opened a PR <#4> a while
back to fix dependencies. It still has not resolved anything on our side
because the changes were not published to NPM. Your NPM page
<https://www.npmjs.com/package/sassdoc-theme-flippant> still shows that
the latest publish was 4 years ago.
Would you kindly publish the dependency updates so we could continue using
your package?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AACIJQRHHAAKZR6MSIOR7P3Q7MAXRA5CNFSM4KLHUUKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IIRPBYA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACIJQRIWNNLPHVBXXVX3OLQ7MAXRANCNFSM4KLHUUKA>
.
|
I merged that change in october. Just pushed a new release out. |
pushed 1.0.1 |
@kyrstenkelly all good? |
Thanks for doing this @dbox. The version does seem to be properly released now. I am however getting a new error when trying to use the theme. Not sure if anything else changed since the last release that could've caused this?
|
Hrm. Dunno. Happy to accept a PR fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My coworker opened a PR a while back to fix dependencies. It still has not resolved anything on our side because the changes were not published to NPM. Your NPM page still shows that the latest publish was 4 years ago.
Would you kindly publish the dependency updates so we could continue using your package?
The text was updated successfully, but these errors were encountered: