Skip to content

feat(manager): bump EVerest to 2026.02.1 - #179

Open
sturman wants to merge 1 commit into
EVerest:mainfrom
sturman:feat/everest-2026.02.1
Open

sturman wants to merge 1 commit into
EVerest:mainfrom
sturman:feat/everest-2026.02.1

Conversation

@sturman

@sturman sturman commented Oct 12, 2026 •

Copy link
Copy Markdown

Bumps the manager image to EVerest 2026.02.1. Supersedes #177.

  • build-kit-base v1.5.5 (ghcr.io/everest/everest-ci); clone from the EVerest/EVerest monorepo
  • .env tag set to 2026.02.1
  • Demo patches that are upstream or no longer apply are dropped: departure time, single phase, composite schedule, 16 A cap, M1 multicast, libocpp logging and cert chain
  • Unit tests disabled in the image build

Open points

  • The demos have not been re-tested against 2026.02.1 yet
  • Do we still need the single-phase / 16 A cap behavior? If so, those patches need porting

Signed-off-by: sturman <4456572+sturman@users.noreply.github.com>
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

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.

1 participant