Hi, can someone describe this more, in terms of:
cause → effect → what happens over time → what should Travis end user do?
I have a .travis.yml for a build, and obviously I tried to keep it as generic and minimalist as possible. It has
dist: bionic
language: node_js
node_js: "stable"
The “stable” does raise questions about Node.js v18: Is someone going to fix something? It seems unfortunate that (for me) it is not stable, because the Node or Linux people did an “intentional” breaking change.
My file has another config
env:
global:
- NODE_ENV=development
Now this - Is this where I could improve things by not referring to “development” but “production”?
What I’m asking is, how can I be asked to code in a version like 17? If my project sits and does occasional builds for years, going forward - if I forget that I did this workaround - then I’m not running latest stuff, I’m not gaining the value of auto-updating, auto-dependencies, the slickness of Docker images etc. Thoughts about this? Thanks