Repository navigation
chore(deps): bump packdb engine/metadata to 5.0.0-pre.0.20261025203222.b00c195f2eaf - #278
Merged
Merged
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Risk: medium. Approved: Cursor Bugbot and Cursor Security Agent completed successfully with no findings that need human review, and this is a lockstep engine/metadata image-pin bump within the configured risk threshold. No prior approval from this automation to re-evaluate.
Sent by Cursor Approval Agent: Infra Reviewer
fstr
changed the title
fstr
force-pushed
the
engine-release/bump-packdb
branch
from
October 12, 2026 06:51
2cb7b93 to
60a5fab
Compare
fstr
changed the title
fstr
force-pushed
the
engine-release/bump-packdb
branch
from
October 19, 2026 06:44
60a5fab to
6bf99ee
Compare
fstr
changed the title
fstr
force-pushed
the
engine-release/bump-packdb
branch
from
October 26, 2026 06:12
6bf99ee to
389d5e9
Compare
gm42
approved these changes
Oct 26, 2026
gm42
pushed a commit
that referenced
this pull request
Oct 26, 2026
Automated release PR. --- ## [0.17.7](firebolt-operator-v0.17.6...firebolt-operator-v0.17.7) (2026-10-26) ### Dependencies * **deps:** bump packdb engine/metadata to 5.0.0-pre.0.20261025203222.b00c195f2eaf ([#278](#278)) ([97f4237](97f4237)) --- This PR was generated with Release Please. Co-authored-by: fireboltdb-ci-writer[bot] <207707662+fireboltdb-ci-writer[bot]@users.noreply.github.com>
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.
Summary
Bump default engine/metadata images to packdb
5.0.0-pre.0.20261025203222.b00c195f2eaf— the build the engine/metadata
:latestGHCR tags were just re-pointed to.Note
Opened automatically by packdb's
v5-weekly-releaseworkflow (weeklyMonday refresh or a manual promotion) right after it re-pointed the
engine/metadata
:latestGHCR tags at this build, so:latestand thisrepo's pinned tags move together. An unmerged PR is overwritten by the
next run.
Note
Low Risk
Only updates pinned pre-release engine/metadata tags used for default builds and E2E; risk is limited to compatibility with the new packdb build, which PR CI is intended to validate.
Overview
Automated packdb image pin refresh for the default
latestbuild variant:ENGINE_TAGandMETADATA_TAGinconfig/images/defaults.latest.envmove fromrelease-5.0.0-pre.0.20260927210425.e91cd5bd17f8torelease-5.0.0-pre.0.20261025203222.b00c195f2eaf, keeping engine and metadata on the same release flavor.No other images or config change—Postgres, Envoy, curl, and engine-web pins are untouched. This tracks the GHCR
:latestpromotion that packdb’s weekly workflow just applied; CI on the PR is meant to catch operator/E2E breakage from the new engine/metadata build.Reviewed by Cursor Bugbot for commit 389d5e9. Bugbot is set up for automated code reviews on this repo. Configure here.