Closes#134
- Dynamically generates the calendar before the export step
- I tested it with google calendar, updates are propagating as expected (it takes a day for google calendar to get updated)
You can try adding this URL to your calendar to test things out: https://csclub.uwaterloo.ca/~a3thakra/csc/adi-ical/events.ics
Reviewed-on: www/www-new#332
Reviewed-by: n3parikh <n3parikh@csclub.uwaterloo.ca>
Co-authored-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Co-committed-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
So that renovate uses npm v7 and not npm v6. Node 14 comes with npm v6,
but node 16 comes with npm v7.
Reviewed-on: www/www-new#150
Co-authored-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Co-committed-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
## All renovate PRs will use npm v7
Up until now, renovate was using npm v6 to generate PRs for dependency updates. Because the lockfile format changed from v6 to v7, there was a very big diff in the what deps we're installing. Enforcing npm v7 in package.json makes renovate use npm v7 as well.
## Added npm v7 and node 14+ restrictions to package.json
This should print out a warning if the user is not using those versions of node and npm.
## CI is upgraded to node 16
The `node:14` image bundles npm v6, and is the current LTS, but `node:16` will be LTS soon (October 2021) and bundles in npm v7. So we might as well move our CI to node 16. Right now, CI is installing deps with npm v6, and things can potentially go wrong with that.
## Enabled the dependency dashboard for renovatebot
This should create an issue that acts as a dashboard for tracking all renovatebot PRs.
Reviewed-on: www/www-new#127
Co-authored-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>
Co-committed-by: Aditya Thakral <a3thakra@csclub.uwaterloo.ca>