Update version to 4.3.1

[jsvob]

see the changelog

[osoukup]

I would await that the change with the new API endpoints extends the API but there is nothing in the diff and regenerating the schema makes no changes. LGTM

[JakubFrejlach]

I would await that the change with the new API endpoints extends the API but there is nothing in the diff and regenerating the schema makes no changes. LGTM

That is because those API endpoint changes were purposely hidden from the API schema:
fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR454
fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR444

Not sure about the actual reason, I guess @MrMarble knows more.

[MrMarble]

I would await that the change with the new API endpoints extends the API but there is nothing in the diff and regenerating the schema makes no changes. LGTM

That is because those API endpoint changes were purposely hidden from the API schema: fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR454 fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR444

Not sure about the actual reason, I guess @MrMarble knows more.

Those endpoints are intended to work only with djangoql comletion library https://github.com/ivelum/djangoql-completion and not directly by the users, that's why I decided to keep them private, like we do with jira_stage_forwarder

osidb/osidb/urls.py

Lines 102 to 108 in 963cbc4

	if get_env() != "prod":
	urlpatterns.append(
	path(
	f"api/{OSIDB_API_VERSION}/jira_stage_forwarder",
	JiraStageForwarderView.as_view(),
	)
	)

no other reason a part from that.
If you think makes sense to document them on the API feel free to include them

[JakubFrejlach]

I would await that the change with the new API endpoints extends the API but there is nothing in the diff and regenerating the schema makes no changes. LGTM

That is because those API endpoint changes were purposely hidden from the API schema: fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR454 fbae64e#diff-4a51610181bd496db117d73122150acb06a494798165c70ce3c1b15252430ceaR444
Not sure about the actual reason, I guess @MrMarble knows more.

Those endpoints are intended to work only with djangoql comletion library https://github.com/ivelum/djangoql-completion and not directly by the users, that's why I decided to keep them private, like we do with jira_stage_forwarder

osidb/osidb/urls.py

Lines 102 to 108 in 963cbc4

	if get_env() != "prod":
	urlpatterns.append(
	path(
	f"api/{OSIDB_API_VERSION}/jira_stage_forwarder",
	JiraStageForwarderView.as_view(),
	)
	)

no other reason a part from that.
If you think makes sense to document them on the API feel free to include them

I see, I guess we don't need to show them to people in this case. Thanks for the explanation.