build(deps): bump debian from 3a39a05 to d7e1218 in /crates/orion-cli - #301
Merged
codetiger merged 3 commits intoSep 1, 2026
Merged
Conversation
Bumps debian from `3a39a05` to `d7e1218`. --- updated-dependencies: - dependency-name: debian dependency-version: trixie-slim dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
orion-docs | 561619d | Sep 01 2026, 07:03 AM |
dependabot
Bot
deleted the
dependabot/docker/crates/orion-cli/debian-d7e1218
branch
September 1, 2026 07:41
codetiger
added a commit
that referenced
this pull request
Sep 1, 2026
…e digest The runtime digest in the server `Dockerfile` had drifted from the one the CLI `Dockerfile` uses: dependabot raised #301 against `crates/orion-cli` only, so the two `debian:trixie-slim` pins named different builds of the same tag. Both now sit on `d7e1218`. The reference stacks move to current stable: - postgres 16 → 18 (`docker-compose.ha.yml`, the Helm dev stack, and the postgres-orders example) - redis 7 → 8 - nginx 1.27 → 1.30. **1.30, not 1.31**: nginx numbers even minors stable and odd minors mainline, so 1.31 is the development branch. `debian:trixie-slim` is already current — trixie is Debian stable — so only its digest moved. **The Rust builder stays on `rust:1.98-slim`.** It is not a stale pin, it is the MSRV: `rust-version = "1.98"` in the root manifest, the `MSRV (1.98)` CI job, and both Dockerfiles are meant to agree, so the shipped binary is built by the oldest toolchain the project claims to support. Raising it is a support policy decision rather than an image refresh, so it is left alone here. The compose files also stop defaulting to 1.4.0, which the 1.5.0 release left behind.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
Cooldown could not be applied because no publication date was available from the registry.
Bumps debian from
3a39a05tod7e1218.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)