Meet the team
See all 1 on GitHub →Commit activity
Last 12 weeks · 1 commit
Community health
4 of 6 standards met
85
✓README✓License✓Contributing✓Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Active · 2 discussions · Last activity 4h ago
See all on GitHub →Recent fixes
I noticed that node.yml workflow, for each matrix configuration, the UUT (project) is built with the selected node version, then the test suite is run on the same node runtime. ie: However, in real life, a dev publishes an NPM package built with one node runtime (say v40), and when users include that package in their projects, they build their projects on their own runtime (say v33), and release the product to end users who run it on a variety or runtimes (say v1-99), ie: Is it valid to assert that if a projects builds on version X and passes the tests on version X for any value of X, then the released package, built on version Y will run correctly on any runtime version from v1-99 ? Shouldn't the release candidate package be tested against all the supported runtimes? Thanks
Structured data for AI agents
Repository: ljharb/actions. Description: GitHub actions I use for CI. Stars: 13, Forks: 3. Primary language: JavaScript. Languages: JavaScript (67.3%), Shell (32.7%). License: MIT. Open PRs: 0, open issues: 2. Last activity: 4h ago. Community health: 85%. Top contributors: ljharb.