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

Update oada-cache dep to 4.0.0 #5

Merged
merged 1 commit into from
Dec 2, 2020
Merged

Update oada-cache dep to 4.0.0 #5

merged 1 commit into from
Dec 2, 2020

Conversation

aaron97neu
Copy link
Contributor

Needed to use with OADAv2 due to returning success/200 issue. Does yarn.lock need to be updated too?

Will npm be updated automatically or does that need to be triggered manually?

Needed to use with OADAv2 due to returning success/200 issue. Does `yarn.lock` need to be updated too?

Will npm be updated automatically or does that need to be triggered manually?
@sanoel
Copy link
Contributor

sanoel commented Dec 2, 2020

Yes, yarn lock files ought to be committed. Npm will need to be triggered manually via npm publish. I can do this. I think most of us have moved over to oada/client and oada-cache-overmind, but I can pull this and publish it.

@sanoel sanoel merged commit 862b6af into OADA:master Dec 2, 2020
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

Successfully merging this pull request may close these issues.

2 participants