v3.2.0

[gnikit]

What's Changed

• Bump lint-staged from 13.0.0 to 13.0.1 by @dependabot in Bump lint-staged from 13.0.0 to 13.0.1 #531
• Bump @typescript-eslint/parser from 5.27.1 to 5.28.0 by @dependabot in Bump @typescript-eslint/parser from 5.27.1 to 5.28.0 #528
• Bump webpack-cli from 4.9.2 to 4.10.0 by @dependabot in Bump webpack-cli from 4.9.2 to 4.10.0 #533
• Bump @typescript-eslint/eslint-plugin from 5.27.1 to 5.28.0 by @dependabot in Bump @typescript-eslint/eslint-plugin from 5.27.1 to 5.28.0 #532
• Bump @vscode/test-electron from 2.1.3 to 2.1.4 by @dependabot in Bump @vscode/test-electron from 2.1.3 to 2.1.4 #529
• Bump @types/node from 16.11.38 to 16.11.39 by @dependabot in Bump @types/node from 16.11.38 to 16.11.39 #530
• Removes redundant tags & language aliases by @gnikit in Removes redundant tags & language aliases #537
• [BUG] linter.modOutput not working for Intel compilers by @gnikit in [BUG] linter.modOutput not working for Intel compilers #539
• Bump eslint from 8.17.0 to 8.18.0 by @dependabot in Bump eslint from 8.17.0 to 8.18.0 #541
• Bump lint-staged from 13.0.1 to 13.0.2 by @dependabot in Bump lint-staged from 13.0.1 to 13.0.2 #545
• Bump prettier from 2.6.2 to 2.7.1 by @dependabot in Bump prettier from 2.6.2 to 2.7.1 #543
• Bump eslint-plugin-jsdoc from 39.3.2 to 39.3.3 by @dependabot in Bump eslint-plugin-jsdoc from 39.3.2 to 39.3.3 #546
• Bump typescript from 4.7.3 to 4.7.4 by @dependabot in Bump typescript from 4.7.3 to 4.7.4 #544
• Bump @typescript-eslint/parser from 5.28.0 to 5.29.0 by @dependabot in Bump @typescript-eslint/parser from 5.28.0 to 5.29.0 #548
• Bump @typescript-eslint/eslint-plugin from 5.28.0 to 5.29.0 by @dependabot in Bump @typescript-eslint/eslint-plugin from 5.28.0 to 5.29.0 #549
• Bump ts-loader from 9.3.0 to 9.3.1 by @dependabot in Bump ts-loader from 9.3.0 to 9.3.1 #551
• Bump @vscode/test-electron from 2.1.4 to 2.1.5 by @dependabot in Bump @vscode/test-electron from 2.1.4 to 2.1.5 #552
• Bump lint-staged from 13.0.2 to 13.0.3 by @dependabot in Bump lint-staged from 13.0.2 to 13.0.3 #558
• Bump eslint-plugin-prettier from 4.0.0 to 4.2.1 by @dependabot in Bump eslint-plugin-prettier from 4.0.0 to 4.2.1 #556
• Bump eslint from 8.18.0 to 8.19.0 by @dependabot in Bump eslint from 8.18.0 to 8.19.0 #557
• Bump @typescript-eslint/parser from 5.29.0 to 5.30.5 by @dependabot in Bump @typescript-eslint/parser from 5.29.0 to 5.30.5 #559
• Bump @typescript-eslint/eslint-plugin from 5.29.0 to 5.30.5 by @dependabot in Bump @typescript-eslint/eslint-plugin from 5.29.0 to 5.30.5 #560
• Add NAG linting by @gnikit in Add NAG linting #562
• Restructured test Fortran code by @gnikit in Restructured test Fortran code #563
• Linter mod output by @gnikit in Linter mod output #564
• chore: Refactors linter routines by @gnikit in chore: Refactors linter routines #565

Full Changelog: v3.1.0...v3.2.0

---

This discussion was created from the release v3.2.0.

[awvwgk]

Maybe worth to split the changelog in actual code base changes and dependency updates. The autogenerated release notes might be able to do this based on the labels on the PR (docs).

[gnikit]

I usually do the GitHub auto-generate release notes but for this release, because it contained so many changes and PRs from almost a year ago I chose not to, because I wanted only the changes that affect the users to be visible. Of course that is not 100% accurate and you can still see some maintenance changes in the official Changelog that users would not care, but I still think it is better than having a 100+ PRs from dependabot. The lesson learned from this was to never again take that long to issue a major release...

On a more general note, Javascript/Typescript projects have amazing dev tools, that autogenerate Changelogs and GitHub release notes, standardise commit messages, linting and lint fixing etc.. I spent a decent amount of time trying to find something that works but I never got around to finishing it.

Currently, we only have pre-commit hooks with husky for linting and formatting. It turns out the changelog/release notes and commit message standardisation is slightly harder to setup.