Skip to content

Update mongo Docker tag to v8.3.13 - #323

Open
renovate[bot] wants to merge 3 commits into
developfrom
renovate/mongo-8.x
Open

renovate[bot] wants to merge 3 commits into
developfrom
renovate/mongo-8.x

Conversation

@renovate

@renovate renovate Bot commented Jun 22, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
mongo (source) patch 8.3.2 → 8.3.13

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 9bdd388 to 51e2e9a Compare July 23, 2026 02:58
@renovate renovate Bot changed the title Update mongo Docker tag to v8.3.4 Update mongo Docker tag to v8.3.7 Jul 23, 2026
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 51e2e9a to a913460 Compare August 12, 2026 01:38
@renovate renovate Bot changed the title Update mongo Docker tag to v8.3.7 Update mongo Docker tag to v8.3.8 Aug 12, 2026
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from a913460 to dbaa2fd Compare September 3, 2026 11:17
@Sheikah45
Sheikah45 force-pushed the develop branch 5 times, most recently from 2f08fdd to ff311f0 Compare September 7, 2026 23:45
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from dbaa2fd to cfac163 Compare September 9, 2026 05:37
@renovate renovate Bot changed the title Update mongo Docker tag to v8.3.8 Update mongo Docker tag to v8.3.9 Sep 9, 2026
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from cfac163 to 6502138 Compare September 15, 2026 02:51
@renovate renovate Bot changed the title Update mongo Docker tag to v8.3.9 Update mongo Docker tag to v8.3.11 Sep 15, 2026
@coderabbitai

coderabbitai Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7cc0b24c-8531-49b8-a242-70af7fc76a5a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@Sheikah45
Sheikah45 force-pushed the develop branch 2 times, most recently from 9f98b63 to f2af959 Compare September 20, 2026 13:53
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 6502138 to ca26270 Compare September 20, 2026 13:53
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from ca26270 to c5046a5 Compare September 25, 2026 04:30
@Sheikah45
Sheikah45 force-pushed the develop branch 3 times, most recently from c3c86e1 to 267571f Compare October 6, 2026 23:36
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from c5046a5 to 0481946 Compare October 14, 2026 05:39
@renovate renovate Bot changed the title Update mongo Docker tag to v8.3.11 Update mongo Docker tag to v8.3.13 Oct 14, 2026
@Sheikah45
Sheikah45 force-pushed the develop branch 3 times, most recently from deba43c to 7dfeb0a Compare October 19, 2026 11:44
@Sheikah45
Sheikah45 force-pushed the develop branch 4 times, most recently from a1c7d06 to fcc7b03 Compare October 22, 2026 01:28
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 0481946 to 1715909 Compare October 22, 2026 02:16
@Sheikah45
Sheikah45 force-pushed the develop branch 6 times, most recently from af606a9 to e1333b8 Compare October 26, 2026 02:41
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 1715909 to 8375492 Compare October 26, 2026 16:41
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from 8375492 to ed8030c Compare October 27, 2026 00:46
Every co-op mission has a thumbnail URL and none of them had a file
behind it. CoopMapEnricher mints
maps/previews/{small,large}/<folder>.vNNNN.png out of the zip name and
never checks that it exists; the vault upload path writes previews in
MapService.generatePreview, but co-op missions do not go through it,
they come through this deployer, which never wrote one. Measured
against the live CDN on 2026-08-21: of 42 mission folders, zero had the
file the API points at.

What clients show instead is whatever art happens to sit in the map
folder, which is why some missions have a preview, some have none, and
two have the wrong one. Operation Red Revenge arrived complete in #417
with preview art from an earlier draft of its own terrain. Tha Atha
Aez is worse: #417 replaced its .scmap and left the .png and .dds from
2017 untouched, so its preview is seven years older than the map and
shows a different one, letterboxed because that map was not square.

Previews are now produced here, from three sources in a fixed order:

  - the preview embedded in the mission's own .scmap (31 missions),
    which is the only source that cannot disagree with the terrain
  - the .dds beside the map (12), for the missions whose map is not in
    this repository at all but part of the game install. Same 256 by
    256 BGRA layout, so the same decoder reads it, and it beats the
    100 by 100 .png next to it
  - the stock map the mission's own _scenario.lua names (1), for Novax
    Station Assault, which has no image of its own anywhere. Its map is
    X1MP_012, whose vault preview already sits in this directory

The order is the point. Both missions with wrong art have a *matching
pair* of wrong sidecars, so a sidecar that could win over a map file
would preserve exactly those two bugs.

Not com.faforever.commons' PreviewGenerator: run over all 44 missions,
all 44 fail. It reads marker art from resources the published data
artifact does not contain (ImageIO gets a null stream), and it takes
marker positions from evaluating _save.lua, which a third of the
campaign missions refuse. Both are the marker overlay, not the picture,
so this takes the picture. The .scmap layout it needs is the one
ScmapPathFixer already walks and CI already verifies byte for byte.

Sizes follow the current vault convention, 128 and 512. The CDN still
carries older 100 and 256 files from before it, which is why the stock
map fall back re-renders rather than copies.

An unchanged mission is never rezipped, so ensureMapPreviews fills in
what is missing on any run: the existing missions get their previews
without waiting to be edited.

verifyCoopPreviews renders every mission in a MAPS_REPO checkout and
reports the source, size and colour count per mission. It fails if a
mission with a real map file produces nothing, if an image is a single
flat colour, or if no mission rendered from its own map file at all.
* add faf-player-service

* use versioned player-service

* add geoip database update
@renovate
renovate Bot force-pushed the renovate/mongo-8.x branch from b5db7e0 to c1ac933 Compare October 31, 2026 17:18
@Sheikah45
Sheikah45 force-pushed the develop branch 2 times, most recently from 3dec1d3 to 97c517a Compare November 1, 2026 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants