build: release v6.42.0

[LinHuiqing]

New

• feat: payment mvp #6095
• build: merge release v6.41.1 to develop #6136
• chore: make hsts header follow recommendation from csa #6106
• feat: track nodejs runtime metrics in APM #6120
• fix: date-picker bug for negative UTC timezones #6096
• chore: prune error logs for ndi oidc key retrieval error #6098
• build: merge release v6.40.0 into develop #6072
• chore: bump version to v6.42.0 39d299f

Dependencies

• fix(deps): bump xml2js and aws-sdk #6084
• fix(deps): bump libphonenumber-js from 1.10.26 to 1.10.28 in /shared #6119
• fix(deps): bump vm2 from 3.9.15 to 3.9.16 #6092
• fix(deps): bump vm2 from 3.9.11 to 3.9.15 #6075
• fix(deps): bump type-fest from 3.7.2 to 3.8.0 in /shared #6064

Dev-Dependencies

• chore(deps-dev): bump @typescript-eslint/eslint-plugin from 5.58.0 to 5.59.0 in /shared #6104
• chore(deps-dev): bump @typescript-eslint/parser from 5.58.0 to 5.59.0 in /shared #6105
• chore(deps-dev): bump @types/lodash from 4.14.192 to 4.14.194 in /shared #6100
• chore(deps-dev): bump @typescript-eslint/eslint-plugin from 5.57.1 to 5.58.0 in /shared #6082
• chore(deps-dev): bump @typescript-eslint/parser from 5.57.1 to 5.58.0 in /shared #6083

Tests

feat: track nodejs runtime metrics in APM #6120

• Go to the APM FormSG service page in DataDog, enter the tab Node.JS Runtime Metrics and verify data is being reported
• Check graphs for CPU load after release, to verify we are still in acceptable range

fix: date-picker bug for negative UTC timezones #6096

To ensure that all our bases are covered, try to test the most extreme timezones. Here are the suggested timezones:

• Most common use case: Singapore - Singapore (UTC +08)
• Negative: Alofi - Niue (UTC -11)
• Positive: Wellington - New Zealand (UTC +12)

Preparation:

• Create a form with a date field and open the form.

For the tests below, timezones A and B refer to the positive and negative timezones mentioned above, in any order.

Ensure that date picker for date field with "Disallow past dates" option exhibits expected behaviour:

1. • Set your timezone as A.
2. • On the admin panel, refresh, select and save the "Disallow past dates" option for the date field.
3. • On the respondent form, refresh and open the date picker. Only the current and future dates of the timezone should be shown.
4. • Select a date. The appropriate date should be reflected in the date field.
5. • Change your device's timezone to B.
6. • Repeat tasks 3-4.
7. • Repeat tasks 2-4.
8. • Change your device's timezone to A.
9. • Repeat tasks 3-4.

Ensure that date picker for date field with "Disallow future dates" option exhibits expected behaviour:

1. • Set your timezone as A.
2. • On the admin panel, refresh, select and save the "Disallow future dates" option for the date field.
3. • On the respondent form, refresh and open the date picker. Only the current and future dates of the timezone should be shown.
4. • Select a date. The appropriate date should be reflected in the date field.
5. • Change your device's timezone to B.
6. • Repeat tasks 3-4.
7. • Repeat tasks 2-4.
8. • Change your device's timezone to A.
9. • Repeat tasks 3-4.

Ensure that date picker for date field with "Custom date range" option exhibits expected behaviour:

1. • Set your timezone as A.
2. • On the admin panel, refresh and select the "Custom date range" option for the date field.
3. • Select a start date.
4. • Open the end date field date picker. Only the dates on or after the selected start date should be selectable.
5. • Select an end date.
6. • Save the selected date range. Optionally, check that the dates saved in the DB are in UTC.
7. • On the respondent form, refresh and open the date picker. Only the dates in the selected date range should be selectable.
8. • Select a date. The respective date should be reflected in the date field.
9. • Change your device's timezone to B.
10. • Repeat tasks 7-8.
11. • Repeat task 2. Ensure that the start and end dates remain the same.
12. • Update the start and end dates for the date field. Save it.
13. • Repeat tasks 7-8.
14. • Change your device's timezone to A.
15. • Repeat tasks 7-8.

Note: Here's how to set your Mac's timezone.

Design/ product question: Should "Disallow past dates" and "Disallow future dates" be taking the past / future based on the admins' timezone, specified timezone or the users' timezone? Also, even when we have decided on the previous question, does it even make sense if the concept of time is not considered? E.g. if the recurring event I want to organise is at 10am, our date picker won't be able to know that so if we have a timezone in mind, it won't "filter" properly. Currently, it's simply implemented based on the users' timezone so its not disorienting.

feat: payment mvp #6095

Refer to Payments QA Google Doc for comprehensive list of manual tests.