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

fix: update npm cache directory #114

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

alessandro-mariotti-zupit
Copy link
Member

Checklist before requesting a review

  • I have performed a self-review of my code
  • Does the code follow the team's coding standards and best practices?
  • Are there any duplicated code blocks that can be refactored into reusable functions?
  • Are there tests on the new code?
  • Does the PR implement the intended functionality or fix the issue described in the title and description?
  • Is the PR title clear and detailed enough to provide necessary context?
  • Have the changes passed the CI/CD pipeline?
  • Will the changes have any adverse effects on other parts of the system and do they work well with other existing features?

@alessandro-mariotti-zupit alessandro-mariotti-zupit merged commit 18a04ad into main Sep 13, 2024
1 check passed
@alessandro-mariotti-zupit alessandro-mariotti-zupit deleted the fix-npm-cache-directory branch September 13, 2024 06:46
alessandro-mariotti-zupit pushed a commit that referenced this pull request Sep 13, 2024
## [1.23.2](v1.23.1...v1.23.2) (2024-09-13)

### Bug Fixes

* update npm cache directory ([#114](#114)) ([18a04ad](18a04ad))
@alessandro-mariotti-zupit
Copy link
Member Author

🎉 This PR is included in version 1.23.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant