-
Notifications
You must be signed in to change notification settings - Fork 12
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
Install Packages post release #482
Conversation
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #482 +/- ##
=======================================
Coverage 73.44% 73.44%
=======================================
Files 240 240
Lines 10180 10180
Branches 1607 1614 +7
=======================================
Hits 7477 7477
- Misses 2612 2622 +10
+ Partials 91 81 -10
|
… package.json not a yarn command. install all tarballs
…ets because of workspace: references in package.jsons try another way of doing if
d4cf677
to
c46a27b
Compare
After plackages are released, attempt to install each of them. combined with prereleasing this should help us catch any issues arising from packages being used outside of development environment
tested
run with mock data
https://github.com/celo-org/developer-tooling/actions/runs/12275055520/job/34249530769?pr=482
PR-Codex overview
This PR updates the GitHub Actions workflows and modifies the
package.json
file for a project, primarily focusing on changing Node.js versions, enhancing package publishing processes, and improving the installation of released packages.Detailed summary
.github/workflows/cron-npm-install.yml.gitignore
.node-version
from18.x
to20.x
in therelease.yaml
workflow.prepack
script inpackage.json
to useyarn run build
.@celo/celocli
.