Skip to content

fix(deps): update felddy/foundryvtt docker tag to v14 (release/foundryvtt-v12) - #369

Closed
wittdennis-renovate[bot] wants to merge 1 commit into
release/foundryvtt-v12from
renovate/release/foundryvtt-v12-felddy-foundryvtt-14.x
Closed

fix(deps): update felddy/foundryvtt docker tag to v14 (release/foundryvtt-v12)#369
wittdennis-renovate[bot] wants to merge 1 commit into
release/foundryvtt-v12from
renovate/release/foundryvtt-v12-felddy-foundryvtt-14.x

Conversation

@wittdennis-renovate

@wittdennis-renovate wittdennis-renovate Bot commented Apr 3, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
felddy/foundryvtt major 12.343.0 → 14.359.0

Release Notes

felddy/foundryvtt-docker (felddy/foundryvtt)

v14.359.0

Compare Source

This container supports Foundry VTT stable release 14.359

See:

[!WARNING]
While this is categorized as a Stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

Important Changes from v13

Primary registry is now GitHub Container Registry

Images are now published primarily to ghcr.io/felddy/foundryvtt. Stable releases continue to be mirrored to Docker Hub at docker.io/felddy/foundryvtt. All documentation and examples have been updated to use ghcr.io image references.

Platform support changes
  • Dropped linux/arm/v7 support.
  • Node.js upgraded from 22 to 24.
  • Base image updated from Debian bookworm to Debian trixie.
New Foundry VTT configuration options

Several new options.json fields introduced in Foundry VTT Version 14 are now configurable via environment variable:

  • FOUNDRY_CSS_THEME — Setup page theme. Default changed from foundry to dark to match Foundry's V14 default.
  • FOUNDRY_DELETE_NEDB — Automatically delete legacy NeDB files after LevelDB migration.
  • FOUNDRY_LOG_SIZE — Maximum log file size before rotation (e.g. 64m).
  • FOUNDRY_MAX_LOGS — Maximum number of log files to retain.
  • FOUNDRY_NO_BACKUPS — Disable automatic world backups before major version migrations.
  • FOUNDRY_SERVICE_CONFIG — Path to a service configuration file.
  • FOUNDRY_SERVICE_KEY — Service authentication key. May be set using secrets.
  • FOUNDRY_TEMP_DIR — Temporary directory for package archive downloads, useful for hosts with constrained /data storage.
  • FOUNDRY_UNIX_SOCKET — Unix domain socket path for the server listener.
  • FOUNDRY_TELEMETRY — Fixed from string passthrough to proper boolean. It is recommended to explicitly set this to avoid a prompt on every container start.
Exponential backoff on container failure

The container now applies exponential backoff before exiting on any failure, protecting the Foundry API servers and your hosting environment from rapid restart loops. Previously, a misconfigured or crashing container could restart immediately and repeatedly — potentially hammering the Foundry download and license servers.

Supply chain security

Container images are now signed and published with verifiable SLSA Level 3 provenance, Software Bills of Materials (SBOMs), and vulnerability attestations via Trivy for every supported platform. These artifacts are attached to each image in the registry. The build pipeline has been upgraded to use felddy/reusable-workflows v4 with attestations: write permissions.

What's Changed

New Contributors

Full Changelog: felddy/foundryvtt-docker@v13.351.0...v14.359.0

v13.351.0

Compare Source

This container supports Foundry VTT stable release 13.351

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

New Contributors

Full Changelog: felddy/foundryvtt-docker@v13.350.0...v13.351.0

v13.350.0

Compare Source

This container supports Foundry VTT stable release 13.350

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.348.0...v13.350.0

v13.348.0

Compare Source

This container supports Foundry VTT stable release 13.348

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

New Contributors

Full Changelog: felddy/foundryvtt-docker@v13.347.0...v13.348.0

v13.347.0

Compare Source

This container supports Foundry VTT stable release 13.347

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.346.0...v13.347.0

v13.346.0

Compare Source

This container supports Foundry VTT stable release 13.346

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.345.0...v13.346.0

v13.345.0

Compare Source

This container supports Foundry VTT stable release 13.345

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.344.0...v13.345.0

v13.344.0

Compare Source

This container supports Foundry VTT stable release 13.344

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.342.2...v13.344.0

v13.342.2

Compare Source

This container supports Foundry VTT stable release 13.342

This release fixes a bug that prevented admin keys passed in as secrets from being properly configured at startup.

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

  • Bump actions/dependency-review-action from 4.6.0 to 4.7.0 in the github-actions-all group by @​dependabot in #​1214
  • Restore exports for variables that are derived from secrets, bump container version by @​felddy in #​1215

Full Changelog: felddy/foundryvtt-docker@v13.342.1...v13.342.2

v13.342.1

Compare Source

This container supports Foundry VTT stable release 13.342

This release fixes a bug that would cause licenses to be installed in the wrong directory.

If you ran container versions 13.340.0, 13.341.0, or 13.342.0, you may have config (lower case c) directory on your /data volume. This directory is unused and can safely be removed or ignored.

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

  • Bump github/codeql-action from 3.28.16 to 3.28.17 in the github-actions-all group by @​dependabot in #​1210
  • Fix Config directory name and bump container version to 13.342.1 by @​felddy in #​1213

Full Changelog: felddy/foundryvtt-docker@v13.342.0...v13.342.1

v13.342.0

Compare Source

This container supports Foundry VTT stable release 13.342

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.341.0...v13.342.0

v13.341.0

Compare Source

This container supports Foundry VTT stable release 13.341

See:

[!WARNING]
While this is categorized as a stable release there is always a possibility of unexpected bugs or compatibility issues. As with any time you update the core software, be sure to perform a complete backup of your user data to minimize any risk of data loss.

Important Changes from v12

There are breaking changes from v12 to v13 of this container around the default
user and group that is used to run Foundry. See this discussion for more information.

  • The container now defaults to a non-root user.
  • The internal home directory has changed from /home/foundry to /home/node
  • FOUNDRY_UID and FOUNDRY_GID environment variables have been deprecated.
    The Docker user option should be used to change the uid and gid of the running processes.
  • The container will no longer change the permissions in the data volume to match the uid and gid of the server. Therefore the CONTAINER_PRESERVE_OWNER environment variable is deprecated.
  • The TIMEZONE environment variable has been replaced by the standard TZ environment variable.
  • Dropping support for linux/arm/v6 and re-adding support for linux/s390x.
  • Moving from Node 18 to Node 22.
  • Base image change from Alpine Linux to Debian Linux.
  • Default user and group moves from 421:421 to the Node container standard of 1000:1000.
  • Support using secrets to build pre-installed versions of the container.
  • Added an early test for volume permissions with informative help output for errors.
  • Downloads and caches smaller "Node" distributions of Foundry instead of Linux which included unused Electron files.

All Changes

Full Changelog: felddy/foundryvtt-docker@v12.331.0...v13.341.0

v13.340.0

Compare Source

This pre-release container supports Foundry VTT testing release 13.340

See:

[!WARNING]
This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!

Important Changes from v12

There were substantial internal changes introduced at release v13.333.0 that may affect some users:

  • The container now defaults to a non-root user.
  • The internal home directory has changed from /home/foundry to /home/node
  • FOUNDRY_UID and FOUNDRY_GID environment variables have been deprecated.
    The Docker user option should be used to change the uid and gid of the running processes.
  • The container will no longer change the permissions in the data volume to match the uid and gid of the server. Therefore the CONTAINER_PRESERVE_OWNER environment variable is deprecated.
  • The TIMEZONE environment variable has been replaced by the standard TZ environment variable.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.339.0...v13.340.0

v13.339.0

Compare Source

This pre-release container supports Foundry VTT testing release 13.339

See:

[!WARNING]
This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!
As always, it is very important to back up your user data before any major update. It is strongly recommended to backup your important Worlds before experimenting with the Testing Build. Better yet, consider taking a full Snapshot.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.338.0...v13.339.0

v13.338.0

Compare Source

This pre-release container supports Foundry VTT testing release 13.338

See:

[!WARNING]
This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!
As always, it is very important to back up your user data before any major update. It is strongly recommended to backup your important Worlds before experimenting with the Testing Build. Better yet, consider taking a full Snapshot.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.337.0...v13.338.0

v13.337.0

Compare Source

This pre-release container supports Foundry VTT testing release 13.337

See:

[!WARNING]
This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!
As always, it is very important to back up your user data before any major update. It is strongly recommended to backup your important Worlds before experimenting with the Testing Build. Better yet, consider taking a full Snapshot.

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.336.0...v13.337.0

v13.336.0

Compare Source

This pre-release container supports Foundry VTT testing release 13.336

See:

[!WARNING]
This Testing update is intended for those dedicated users who wish to test the new features provided in Version 13. It is not intended for use in weekly games or in games with heavy use of add-on modules. The goal for this build is to collect preliminary testing feedback from developers and users, not to power actual game sessions!

What's Changed

Full Changelog: felddy/foundryvtt-docker@v13.335.0...v13.336.0

v13.335.0

Compare Source

This pre-release container supports Foundry VTT development release 13.335

See:

[!WARNING]
Updates on the development channel are intended for testing and feedback from

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • 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 has been generated by Renovate Bot.

@wittdennis wittdennis closed this Apr 3, 2026
@wittdennis
wittdennis deleted the renovate/release/foundryvtt-v12-felddy-foundryvtt-14.x branch April 3, 2026 06:30
@wittdennis-renovate

wittdennis-renovate Bot commented Apr 3, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 14.x releases. But if you manually upgrade to 14.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@wittdennis wittdennis

Labels

bot renovate update:major

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@wittdennis