Skip to content

build: v50#88

Open
alpeb wants to merge 2 commits into
mainfrom
alpeb/dev_50
Open

build: v50#88
alpeb wants to merge 2 commits into
mainfrom
alpeb/dev_50

Conversation

@alpeb

@alpeb alpeb commented Jun 26, 2026

Copy link
Copy Markdown
Member

Ran just sync-k3s-images and just update-versions. Then:

In Dockerfile:

  • RUST_TAG was reverted back to 1.90.0; that should be incremented separately in concert with the other reports
  • helm was manually bumped to v3.21.2; not jumpting straight into v4 just yet
  • bumped NODE to v26 in Dockerfile
  • bumped k3d to 5.9.0
  • bumped PROTOC_GEN_GO_TAG to v1.36.11
  • bumped PROTOC_GEN_GO_GRPC_VERSION to v1.6.2
  • bumped hokay to v0.2.3
  • bumped MARKDOWNLINT_VERSION to 0.22.1

in justfile:

  • set minimum-k8s to 31

In setup-go/action.yml:

  • bumped go to 1.26

@alpeb alpeb force-pushed the alpeb/dev_50 branch 3 times, most recently from 7a92b5e to c7ebd17 Compare June 26, 2026 19:35
Ran `just sync-k3s-images` and `just update-versions`. Then:

In Dockerfile:

- `RUST_TAG` was reverted back to `1.90.0`; that should be incremented separately in concert with the other reports
- helm was manually bumped to `v3.21.2`; not jumpting straight into v4 just yet
- bumped NODE to v26 in Dockerfile
- bumped k3d to 5.9.0
- bumped PROTOC_GEN_GO_TAG to v1.36.11
- bumped PROTOC_GEN_GO_GRPC_VERSION to v1.6.2
- bumped hokay to v0.2.3
- bumped MARKDOWNLINT_VERSION to 0.22.1

in justfile:
- set `minimum-k8s` to 31

In setup-go/action.yml:
- bumped go to 1.26
Comment thread actions/setup-tools/action.yml Outdated
version:
description: Container image version
default: v48
default: v49

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be v50?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now I remember there was some chicken-and-egg problem in this repo. If I set it to v50, the actions.yml workflow will call it and fail because v50 is not published yet. So I'll change this to v50, publish the new image from this branch, and the PR should go green.

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