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

NOT READY - Switching to GitHub Actions npm Cache and Automating package-lock.json #772

Open
wants to merge 45 commits into
base: main
Choose a base branch
from

Conversation

cockroacher
Copy link
Collaborator

Exciting update! We're moving to use the GitHub Actions npm cache via actions/setup-node. This change will help speed up our CI/CD pipeline by caching npm dependencies, which means faster builds and more efficient workflows.

Additionally, we're starting to use package-lock.json to ensure consistent dependency versions across all environments. To make things even smoother, we've set up an automation that updates the package-lock.json file with every release. This ensures that our dependencies are always up-to-date and reduces the risk of version conflicts.

@cockroacher cockroacher added the enhancement New feature or request label Dec 13, 2024
@cockroacher cockroacher changed the title Switching to GitHub Actions npm Cache and Automating package-lock.json NOT READY - Switching to GitHub Actions npm Cache and Automating package-lock.json Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants