chore(release): release v0.3.2

What does this MR do and why?

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

added Category:Wiki glql groupknowledge labels

assigned to @himkp

added devopsplan sectiondev labels

enabled automatic add to merge train when checks pass

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@jachapman (UTC+0, 1 hour behind author)	@digitalmoksha (UTC-6, 7 hours behind author)

Generated by Danger

started a merge train

mentioned in commit 92a01702

merged

changed milestone to %17.8

added typemaintenance label