Releases: maproulette/maproulette-backend
Releases · maproulette/maproulette-backend
v4.4.16
[v4.4.16] - 2024-5-14
Released with maproulette3_v3.15.1
What Changed
- Add feature id filter to search parameters by @CollinBeczak in #1108
- Add support for relations in overpass queries by @CollinBeczak in #1106
- Fix nearby task looping too hard tasks issue by @CollinBeczak in #1110
- Adjust bundling endpoints and add resetTaskBundle endpoint by @CollinBeczak in #1107
Full Changelog: v4.4.15...v4.4.16
v4.4.15
What's Changed
- Improve stability by disabling dynamic leaderboard queries by @ljdelight in #1105
Investigation over several outages has found that some leaderboards in specific cases will run dynamic queries instead of using the pre-computed data, and those dynamic queries cause significant overhead issues and negatively impacts maproulette stability. The below leaderboards will not function (backend will return http 400) until a workaround or alternative solution is determined:
- Project-specific leaderboards
- Challenge-specific leaderboards
- Leaderboards featuring items not currently enabled
- Country-specific leaderboards, excluding the global leaderboard, when multiple countries are selected
- Any use of custom date ranges outside the predefined set of durations
Full Changelog: v4.4.14...v4.4.15
v4.4.14
What's Changed
- Enhance Country Leaderboard Availability During Refresh by @ljdelight in #1099
- Enhance Leaderboard Availability During Refresh by @ljdelight in #1101
- Migrate to io.github.play-swagger and update swagger-ui by @ljdelight in #1103
- add metaReviewedBy object to task history log by @CollinBeczak in #1100
- add unlocked tasks only restriction to bundling and lock tasks on bundle by @CollinBeczak in #1104
Full Changelog: v4.4.13...v4.4.14
v4.4.13
What's Changed
- Improve 'updateLocations' Task for Database Efficiency by @ljdelight in (#1096)
- Require user for leaderboard and topChallenges by @ljdelight in (#1098)
Full Changelog: v4.4.12...v4.4.13
v4.4.12
What's Changed
- Move all remaining comment parameters to the request body of their endpoints by @CollinBeczak in #1094
Full Changelog: v4.4.11...v4.4.12
v4.4.11
What's Changed
- Support adding/removing superuser role via API by @ljdelight in #1078
- Use more verbose logging for development by @ljdelight in #1081
- Create 'maproulette-request-id' for http requests by @ljdelight in #1088
- replace status name Too Hard in API docs by @jschwarz2030 in #1075
- Don't listen for changes on the prod logback.xml by @ljdelight in #1089
- Move comments parameters into Request Body by @CollinBeczak in #1091
Full Changelog: v4.4.10...v4.4.11
v4.4.10
What's Changed
- Allow for an empty 'maproulette.super.accounts' in the config by @ljdelight in #1072
- Fix build badge in README and use GH actions/setup-java@v3 by @ljdelight in #1073
- Use 'warn' logging in bootstrap instead of 'info' by @ljdelight in #1074
- MPExceptionUtil: Log http 403 Forbidden, 404 NotFound, at WARN level without stack by @ljdelight in #1076
- add system notices endpoint by @jschwarz2030 in #1077
Full Changelog: v4.4.9...v4.4.10
v4.4.9
What's Changed
- Handle taskWidgetLayout as JSON object in ChallengeController and MRS… by @ljdelight in #1068
- change unbundleTasks to POST from GET by @CollinBeczak in #1070
- remove unique name constraint on virtual challenges by @CollinBeczak in #1069
- Enable ProjectAPIIntegrationTest tests during GH Action builds by @ljdelight in #1071
Full Changelog: v4.4.8...v4.4.9
v4.4.9-prerelease
Handle taskWidgetLayout as JSON object in ChallengeController and MRS…
v4.4.8
[v4.4.8] - 2023-10-17
Release with maproulette3_v3.13.2
Features
- Added an optional JSON field
taskWidgetLayout
to theChallenge
model to store configurations and data related to task widget layout. - Inserted
taskWidgetLayout
into JSON bodies in theChallengeController
. - Updated GraphQL schema,
MRSchemaTypes
, to include the new field. - Modified the
ChallengeRepository
andChallengeDAL
to handle CRUD operations related to the new field. - Added the corresponding database evolution script to create the new column in the
challenges
table.