You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In direct express dependencies, run a CI job on PR and push to pull down express, npm link/install the local package, run tests.
Benefits
Early detection of breaking changes
Reduce the manual labor of checking if a package change impacts express functionality
Could automatically alert the TC to especially impactful changes we should pay attention to
more words
Not as a blocker on merge of course, but as a quick heads up to signal if a change would break something in express. For both the submitter and the reviewer.
This style of CI is new to me. Its unclear how/if we "get back to green". Specifically, ci that is always red isnt useful. We can code for that though in the ci or alert system, notifying humans on newly failed tests. First pass would just be running express tests and exit 0 or 1
It would of course likely fail when working on a package major not being used by the express version being tested against.
This thought is inspired by discussions in tc chat about greater maintainer autonomy and change awareness in the individual packages.
Independent of that topic, I see value in CITGM style tests.
Reacted by Wes Todd, Chris de Almeida and Sebastian Beltran
CITGM is currently a challenge when we do releases in Node. This will helps us to anticipate issues ahead of releases ❤️.
Aside of targeting commits from our side on > push. I will suggest to trigger this workflow based on cron jobs so we can test this against the last canary release available, etc... Otherwise our anticipation will be very limited.
Obviously we can add some notifications (issues) in case that the actual tests fails and not due binaries availability.
How WIBY works right now, I don't think it's ideal for Express, since we would have to create a GitHub token between the repositories with write permissions. I am working to make this unnecessary, which is something I will be working on these months (see pkgjs/wiby#154).
Activity
jonchurch commentedon Nov 13, 2024
havent tested this yet
ljharb commentedon Nov 13, 2024
see also https://npmjs.com/wiby
UlisesGascon commentedon Nov 14, 2024
I love this idea a lot!
CITGM is currently a challenge when we do releases in Node. This will helps us to anticipate issues ahead of releases ❤️.
Aside of targeting commits from our side
on > push. I will suggest to trigger this workflow based on cron jobs so we can test this against the last canary release available, etc... Otherwise our anticipation will be very limited.Obviously we can add some notifications (issues) in case that the actual tests fails and not due binaries availability.
cc:@marco-ippolito and @RafaelGSS for sure they can add much more context and ideas here 👍
bjohansebas commentedon Mar 3, 2025
How WIBY works right now, I don't think it's ideal for Express, since we would have to create a GitHub token between the repositories with write permissions. I am working to make this unnecessary, which is something I will be working on these months (see pkgjs/wiby#154).
Here's an example of how it works right now (bjohansebas/body-parser#1, bjohansebas/express#1).
bjohansebas commentedon Jul 3, 2025
In about two weeks I'm going on vacation, so I'll be able to dedicate some time to this.